Óscar Fuentes wrote:
Óscar Fuentes <[EMAIL PROTECTED]> writes:
Bill Hoffman <[EMAIL PROTECTED]>
writes:
[about using shell backquotes embedded on link commands through
`target_link_libraries']
I don't even think this will work with cmake 2.6.0, because we use
link scripts.
It is working wi
Óscar Fuentes <[EMAIL PROTECTED]> writes:
> Bill Hoffman <[EMAIL PROTECTED]>
> writes:
[about using shell backquotes embedded on link commands through
`target_link_libraries']
>> I don't even think this will work with cmake 2.6.0, because we use
>> link scripts.
>
> It is working with 2.6.1 and
Bill Hoffman <[EMAIL PROTECTED]>
writes:
>> I just realized another reason why your proposal is not adequate: the
>> libraries and the script must be built before the executable, so, at
>> cmake time, the libraries and the script does not exists.
>>
>> I know this is not portable, but it is intend
Mike Jackson <[EMAIL PROTECTED]> writes:
> Just out of curiosity..
>
> Is the dependency tracking in CMake not adequate enough for your
> project?
No, see below.
> If CMake is used as intended you should not have to manually
> figure out what libraries are needed, CMake should be able to do that
Óscar Fuentes wrote:
Bill Hoffman <[EMAIL PROTECTED]>
writes:
Solved:
target_link_libraries(myexe "`/path/to/script arg1 arg2`")
This is in general a non-portable way to write cmake files, and is not
guaranteed to work in any version of CMake. This is the same as a
pkg-config script. The w
On Aug 11, 2008, at 8:33 PM, Óscar Fuentes wrote:
Bill Hoffman <[EMAIL PROTECTED]>
writes:
Solved:
target_link_libraries(myexe "`/path/to/script arg1 arg2`")
This is in general a non-portable way to write cmake files, and is
not
guaranteed to work in any version of CMake. This is the s
Bill Hoffman <[EMAIL PROTECTED]>
writes:
>> Solved:
>>
>> target_link_libraries(myexe "`/path/to/script arg1 arg2`")
>>
> This is in general a non-portable way to write cmake files, and is not
> guaranteed to work in any version of CMake. This is the same as a
> pkg-config script. The way to do
Bill Hoffman <[EMAIL PROTECTED]>
writes:
>> Solved:
>>
>> target_link_libraries(myexe "`/path/to/script arg1 arg2`")
>>
> This is in general a non-portable way to write cmake files, and is not
> guaranteed to work in any version of CMake. This is the same as a
> pkg-config script. The way to do
Óscar Fuentes wrote:
Óscar Fuentes <[EMAIL PROTECTED]> writes:
[snip]
Solved:
target_link_libraries(myexe "`/path/to/script arg1 arg2`")
This is in general a non-portable way to write cmake files, and is not
guaranteed to work in any version of CMake. This is the same as a
pkg-config scrip
Óscar Fuentes <[EMAIL PROTECTED]> writes:
[snip]
Solved:
target_link_libraries(myexe "`/path/to/script arg1 arg2`")
--
Oscar
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
We have a shell script that computes the list of libraries that shall
appear on the link comand for every executable. The command looks like
this:
g++ ...flags... object-files... -o myexe `/path/to/script arg1 arg2`
Trying to replicate this with CMake is difficult. My first try was to
put the bac
11 matches
Mail list logo