kordejong / hello_cmake Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 328 KB

Project for trying out CMake code

Shell 76.85% C++ 20.75% C 2.40%

hello_cmake's People

Watchers

hello_cmake's Issues

Greeter must be able to use world's target while they are built but not yet installed

World's targets must be exported during a build too. Currently they are exported during an install only.

Figure out a unit testing strategy using Boost.Test and CTest

Figure out how to:

Easily create unit test exes per test case using Boost.Test.
Easily manage execution of all test cases using CTest.

Make sure greeter's package contains world's targets too

Fixup install location to create self contained package (a zip)

Make sure it works on all platforms.

Tasks:

Make sure all shared libraries that are not already in the install location need to be copied into the install location. Note that shared libraries that are copied may depend on yet other shared libraries.
Linux
- Update the rpath setting of all shared libraries in the install location. It must be a relative path.
MacOS
- Update library identification name.
- Update install names of packaged shared libraries that the packaged exes/dlls depend on.

After installing the greeter exe it should find world's shared lib

It should be possible to run greeter-shared from the install location without changing the environment settings.

Make sure greeter's package contains world's targets too

After installing the greeter exe it should find world's shared lib

It should be possible to run greeter-shared from the install location without changing the environment settings.

Clearly separate configs when configuring project's install rules

Use COMPONENT argument of CMake's INSTALL function to distinguish between INSTALL rules for developers and rules for end-users.

After installing the greeter exe it should find world's shared lib (Linux)

It should be possible to run greeter-shared from the install location without changing the environment settings.

After moving the installed greeter project, the greeter exe should find world's shared lib (Windows)

It should be possible to run greeter-shared from the moved install location without changing the environment settings.

Make sure the Python extension works (Linux)

Greeter package must contain all external dlls

After building the greeter exe it should find world's shared lib (Linux)

It should be possible to run greeter-shared from the build location without changing the environment settings.

Make sure the Python extension works (MacOS)

Make sure greeter's package contains world's targets too

Rework build script to install in single location

If both the world and greeter project install in the same location, greeter's targets will find world's shared library automatically.

Afterwards, we can 'fixup' the install location to create a self-contained package (a zip).

After building the greeter exe it should find world's shared lib (MacOS)

It should be possible to run greeter-shared from the build location without changing the environment settings.

After moving the installed greeter project, the greeter exe should find world's shared lib (Linux)

It should be possible to run greeter-shared from the moved install location without changing the environment settings.

Make sure the Python extension works (Windows)

After moving the installed greeter project, the greeter exe should find world's shared lib (MacOS)

It should be possible to run greeter-shared from the moved install location without changing the environment settings.

After building the greeter exe it should find world's shared lib (Windows)

It should be possible to run greeter-shared from the build location without changing the environment settings.

kordejong / hello_cmake Goto Github PK

hello_cmake's People

Watchers

hello_cmake's Issues

Recommend Projects

Recommend Topics

Recommend Org