Ah well, I figured out the problem, it was located between my
chair and my keyboard. Everything works perfectly now. I sure
do love cmake.
Thanks,
Russell
On 01/09/18 15:46, Russell L. Carter wrote:
Greetings,
I am trying to generate a platform specific file by copying it from
the source
Greetings,
I am trying to generate a platform specific file by copying it from
the source tree into a specific directory in the separate
out-of-source build tree. The file generation works fine.
When I try the following cmake code:
set(target_dir ${CMAKE_BINARY_DIR}/nail/platform)
message("tar
ninstall COMMAND echo "\nRemoving installed
>> files:" COMMAND cat
>> ${CMAKE_CURRENT_BINARY_DIR}/install_manifest.txt | xargs rm -fv
>> VERBATIM )
>>
>> See the docs:
>> http://www.cmake.org/cmake/help/v3.0/command/add_custom_target.html
>>
Hi,
With this cmake code:
ADD_CUSTOM_TARGET(uninstall
COMMAND echo "\nRemoving installed files:"
COMMAND cat ${CMAKE_CURRENT_BINARY_DIR}/install_manifest.txt | xargs
rm -fv
)
(sorry about the wrapping...)
the ninja generator fails with:
ninja: error: build.ninja:90: expected '=', got lex
On 01/30/2012 03:09 PM, Eric Noulard wrote:
> 2012/1/30 Russell L. Carter :
[...]
>> I would like to get rid of the "lib" prefix. I am happy with the
>> default suffix generation. Is there an easy way to get rid of the
>> "lib" prefix?
>>
[
Greetings,
I see from the docs that using add_library to build a MODULE results
in the module being named according to the "conventions of the native
platform (such as lib.a or .lib)". And indeed MODULE
names are so generated, as I see from actually building one.
I would like to get rid of the
Hi all,
I have three g++ versions installed. Debian's native g++-4.3 and
g++-4.4 both use /usr/lib/libstdc++.so.6.13, while
/usr/local/bin/g++-4.5 needs /usr/local/lib64/libstdc++.so.6.14.
If I use CXX=/usr/local/bin/g++-4.5 at configure time, executables
are linked against /usr/lib/libstdc++.so.
On 11/08/2010 12:59 PM, Alexander Neundorf wrote:
>
> To get the last component of a path, use
> get_filename_component(... NAME)
> To get the parent directory, use
> get_filename_component(... PATH)
>
>
> When you need to generate a unique name from a path, you could use the
> STRING() comman
On 11/07/2010 01:49 AM, Michael Hertling wrote:
> On 11/07/2010 02:07 AM, Russell L. Carter wrote:
>>
>> Hi there,
>> Happy cmake user here. I want to retrieve the leaf name of
>> the directory property "PARENT_DIRECTORY". This is really
>> a
Hi there,
Happy cmake user here. I want to retrieve the leaf name of
the directory property "PARENT_DIRECTORY". This is really
a more general cmake question: how do I most efficiently
manipulate path components of the absolute pathnames that
cmake uses and returns for many variables?
In the cu
Howdy,
I see there is a PARENT_DIRECTORY property on the current source
dir for all dirs but the top level dir, where the docs state the
property returns an empty string. What would be The Cross
Platform CMAKE Way for getting the parent directory of the top
level cmake directory path?
Thanks,
Ru
ge (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the
Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__
Linux-powered Science
______
--
Russell L. Carter
Esturion, LLC
2285 Sandia Dr
Greetings,
I am new to cmake and am encountering this error when
I try to build a trivial Fortran library:
[EMAIL PROTECTED] [216] make
Scanning dependencies of target hwode
make[2]: *** No rule to make target `SET.mod.proxy', needed by
`hwode/CMakeFiles/hwode.dir/dop853.o.requires'. Stop.
mak
13 matches
Mail list logo
