[CMake] Path to installed target
Michael Wild
themiwi at gmail.com
Wed Jan 12 08:04:05 EST 2011
On 01/12/2011 01:48 PM, Alexey Livshits wrote:
>> Yes, make the tests run without installation. To give more advice, we'd
>> need to know more about those "dependencies". Are they other
>> executables? Data files? Libraries?
>
> Well, if I could do that, I wouldn't ask ;)
> I have 2 versions, which are built from the same sources. So I have to
> have 2 different output directories. Some shared libraries are built
> only for one version, but needed for both. CMake install process helps
> perfectly here.
> Some tests require shared libraries from both versions. So I created
> the new install component for tests, but I cannot address them for
> CTest.
Sorry, I'm still confused. What I understand is that you have e.g.:
src/
|--foo/ # shared library bar
| |-- fooa.c
| |-- foob.c
| `-- fooc.c
`--bar/ # shared libraries foo1 and foo2, both link against bar
|-- bara.c
`-- barb.c
test/
|-- testa.c # requires foo1
|-- testb.c # requires foo2
`-- testc.c # requires both, foo1 and foo2
What I don't understand is whether foo1 and foo2 are actually
conflicting or not (they would be if one was a debug version and the
other a release version, they wouldn't be conflicting if e.g. one was a
single-precision version where all the symbols have a *f suffix and the
other was a double-precision version where the symbols have a *d suffix).
Further, are the tests linking against foo1 and foo2, or are those
plugins (i.e. dynamically loaded)?
If you don't explain the problem more clearly, people won't be able to
help you; particularly because I suspect that you are asking the wrong
question...
Michael
More information about the CMake
mailing list