Re: [CMake] CPack tar ownership
As a side issue: not all platforms which support the TGZ natively support fakeroot. I think ownership rights should likely be a CPACK option as a result. Cheers, Tim On Sat, Jan 8, 2011 at 8:22 AM, Eric Noulard wrote: > 2011/1/8 Tim St. Clair : >> This will be across several *nix platforms, >> >> I tried fakeroot but when I expand it has the euid of the user. > > This is odd, by the way which version of CMake are you using? > > On my ubuntu 10.04 box with CMake 2.8.3, I get: > > A) cpack -G TGZ > leads to a tar+gz archive whose content its owned by the user. > (as printed out using 'tar ztvf file.tgz') > > B) fakeroot cpack -G TGZ > leads to a tar+gz archive whose content its owned by root. > (as printed out using 'tar ztvf file.tgz') > > > An alternative solution would be to force ownership on extraction, > GNU tar has the option: > --no-same-owner > extract files as yourself > > which should do the job (I suppose you can be root when extracting). > > > Do you have any self contained example which exhibits the problem? > > -- > Erk > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack tar ownership
Thanks! I think I botched my 1st verification... fakeroot gives me a root owned package, which expands correctly using tar --no-same-owner -xzf. w00t, Tim On Sat, Jan 8, 2011 at 8:22 AM, Eric Noulard wrote: > 2011/1/8 Tim St. Clair : >> This will be across several *nix platforms, >> >> I tried fakeroot but when I expand it has the euid of the user. > > This is odd, by the way which version of CMake are you using? > > On my ubuntu 10.04 box with CMake 2.8.3, I get: > > A) cpack -G TGZ > leads to a tar+gz archive whose content its owned by the user. > (as printed out using 'tar ztvf file.tgz') > > B) fakeroot cpack -G TGZ > leads to a tar+gz archive whose content its owned by root. > (as printed out using 'tar ztvf file.tgz') > > > An alternative solution would be to force ownership on extraction, > GNU tar has the option: > --no-same-owner > extract files as yourself > > which should do the job (I suppose you can be root when extracting). > > > Do you have any self contained example which exhibits the problem? > > -- > Erk > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack tar ownership
This will be across several *nix platforms, I tried fakeroot but when I expand it has the euid of the user. Cheers, Tim On Fri, Jan 7, 2011 at 6:33 PM, Eric Noulard wrote: > 2011/1/7 Tim St. Clair : >> Is there a way to make all entries in the tar package are owned by >> root, vs. build user. > > On which platform? > Linux ? Debian? Fedora? > > Did you try using "fakeroot" ? > > > -- > Erk > Membre de l'April - « promouvoir et défendre le logiciel libre » - > http://www.april.org > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack tar ownership
Is there a way to make all entries in the tar package are owned by root, vs. build user. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack WiX(.msi) Patch
Folks - I've opened a ticket http://public.kitware.com/Bug/view.php?id=11575 to include my WiX patch I made a while back, and updated to target 2.8.3 src. Please update said ticket with your questions/comments/complaints as I'm determined to get this in your next point release. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ExternalProject_Add + issues with env & auto-conf.
On Wed, Oct 20, 2010 at 8:19 AM, Bill Hoffman wrote: > On 10/20/2010 9:08 AM, Tim St. Clair wrote: >> >> correction, I can see this issue with 2.8.2 i386 binaries vs. hand build. >> > > Tim, it is still unclear to me what your problem is when using ExternalProject_Add with hand built version of cmake 2.8.2 seems to have a series of issues with auto tools relating to the env, the afore mentioned example is a direct repo. Where it will fail in RHEL 5.5 re-running aclocal (when I don't believe it should run at all) >and where you are getting the binaries from. cmake.org > > So, a few questions: > > 1. Where did the binaries come from (i.e. cmake.org, some distro?) cmake.org > 2. Does the hand build 2.8.2 work? yes, except for the above issue. > 3. What exactly is the error you are seeing? see above. > 4. How could one try to reproduce the error? repro, was given in 1st email chain. Simply create a external project with the bits above. I will be on distcomp#cmake if you need more info. nick: tstclair > > -Bill > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ExternalProject_Add + issues with env & auto-conf.
correction, I can see this issue with 2.8.2 i386 binaries vs. hand build.
On Wed, Oct 20, 2010 at 7:40 AM, Tim St. Clair wrote:
> 2.8.0 vs. 2.8.2 hand made
>
> On Tue, Oct 19, 2010 at 4:24 PM, David Cole wrote:
>> What version are these stock i386 binaries you speak of?
>> Where did they come from?
>> For 2.8.1 and earlier the problem did not exist.
>> For 2.8.2, the problem did exist.
>> It should be fixed again in 2.8.3-rc2 and later.
>>
>>
>> On Tue, Oct 19, 2010 at 4:18 PM, Tim St. Clair wrote:
>>>
>>> b4 I do this, because it's a non-trivial investment on a
>>> non-heterogeneous build cluster, can you explain why the i386 stock
>>> binaries behave differently?
>>>
>>> Cheers,
>>> Tim
>>>
>>> On Tue, Oct 19, 2010 at 2:58 PM, Bill Hoffman
>>> wrote:
>>> > Try the 2.8.3 release candidate.
>>> >
>>> > In 2.8.2 the untar did not preserve file times, and this could cause
>>> > auto-make to rerun when it really did not need to.
>>> >
>>> > -Bill
>>> >
>>> >
>>> > On 10/19/2010 3:21 PM, Tim St. Clair wrote:
>>> >>
>>> >> I've been able to consistently repro an issue using
>>> >> ExternalProject_Add w/a configure build of cmake v.s. the i386
>>> >> binaries online shows an issue whenever a it tries to call auto-conf
>>> >> or auto-make as if the environment is hosed. When I use the stock
>>> >> i386 binaries I do not see this issue and I'm able to build external
>>> >> projects.
>>> >>
>>> >> The test example in question is the following:
>>> >>
>>> >>
>>> >> set (LIBXML2_VER libxml2-2.7.3 )
>>> >> ExternalProject_Add( libxml2
>>> >> DEPENDS zlib
>>> >> PREFIX
>>> >> ${EXTERNAL_BUILD_PREFIX}/${LIBXML2_VER}
>>> >> #-- Download Step --
>>> >> DOWNLOAD_COMMAND wget -N
>>> >> http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz ${CMD_TERM}
>>> >> DOWNLOAD_DIR ${EXTERNAL_DL}
>>> >> URL
>>> >> http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz
>>> >> #--Configure step --
>>> >> CONFIGURE_COMMAND ./configure
>>> >> --prefix=${EXTERNAL_STAGE}
>>> >> --disable-shared --with-zlib=${EXTERNAL_STAGE}
>>> >> #--Build Step --
>>> >> BUILD_COMMAND make
>>> >> BUILD_IN_SOURCE 1
>>> >> #--install Step --
>>> >> INSTALL_DIR ${EXTERNAL_STAGE}
>>> >> INSTALL_COMMAND make install )
>>> >
>>> >
>>> > --
>>> > Bill Hoffman
>>> > Kitware, Inc.
>>> > 28 Corporate Drive
>>> > Clifton Park, NY 12065
>>> > bill.hoff...@kitware.com
>>> > http://www.kitware.com
>>> > 518 881-4905 (Direct)
>>> > 518 371-3971 x105
>>> > Fax (518) 371-4573
>>> > ___
>>> > Powered by www.kitware.com
>>> >
>>> > Visit other Kitware open-source projects at
>>> > http://www.kitware.com/opensource/opensource.html
>>> >
>>> > Please keep messages on-topic and check the CMake FAQ at:
>>> > http://www.cmake.org/Wiki/CMake_FAQ
>>> >
>>> > Follow this link to subscribe/unsubscribe:
>>> > http://www.cmake.org/mailman/listinfo/cmake
>>> >
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> Timothy St. Clair
>>> ___
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the CMake FAQ at:
>>> http://www.cmake.org/Wiki/CMake_FAQ
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.cmake.org/mailman/listinfo/cmake
>>
>>
>
>
>
> --
> Cheers,
> Timothy St. Clair
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ExternalProject_Add + issues with env & auto-conf.
2.8.0 vs. 2.8.2 hand made
On Tue, Oct 19, 2010 at 4:24 PM, David Cole wrote:
> What version are these stock i386 binaries you speak of?
> Where did they come from?
> For 2.8.1 and earlier the problem did not exist.
> For 2.8.2, the problem did exist.
> It should be fixed again in 2.8.3-rc2 and later.
>
>
> On Tue, Oct 19, 2010 at 4:18 PM, Tim St. Clair wrote:
>>
>> b4 I do this, because it's a non-trivial investment on a
>> non-heterogeneous build cluster, can you explain why the i386 stock
>> binaries behave differently?
>>
>> Cheers,
>> Tim
>>
>> On Tue, Oct 19, 2010 at 2:58 PM, Bill Hoffman
>> wrote:
>> > Try the 2.8.3 release candidate.
>> >
>> > In 2.8.2 the untar did not preserve file times, and this could cause
>> > auto-make to rerun when it really did not need to.
>> >
>> > -Bill
>> >
>> >
>> > On 10/19/2010 3:21 PM, Tim St. Clair wrote:
>> >>
>> >> I've been able to consistently repro an issue using
>> >> ExternalProject_Add w/a configure build of cmake v.s. the i386
>> >> binaries online shows an issue whenever a it tries to call auto-conf
>> >> or auto-make as if the environment is hosed. When I use the stock
>> >> i386 binaries I do not see this issue and I'm able to build external
>> >> projects.
>> >>
>> >> The test example in question is the following:
>> >>
>> >>
>> >> set (LIBXML2_VER libxml2-2.7.3 )
>> >> ExternalProject_Add( libxml2
>> >> DEPENDS zlib
>> >> PREFIX
>> >> ${EXTERNAL_BUILD_PREFIX}/${LIBXML2_VER}
>> >> #-- Download Step --
>> >> DOWNLOAD_COMMAND wget -N
>> >> http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz ${CMD_TERM}
>> >> DOWNLOAD_DIR ${EXTERNAL_DL}
>> >> URL
>> >> http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz
>> >> #--Configure step --
>> >> CONFIGURE_COMMAND ./configure
>> >> --prefix=${EXTERNAL_STAGE}
>> >> --disable-shared --with-zlib=${EXTERNAL_STAGE}
>> >> #--Build Step --
>> >> BUILD_COMMAND make
>> >> BUILD_IN_SOURCE 1
>> >> #--install Step --
>> >> INSTALL_DIR ${EXTERNAL_STAGE}
>> >> INSTALL_COMMAND make install )
>> >
>> >
>> > --
>> > Bill Hoffman
>> > Kitware, Inc.
>> > 28 Corporate Drive
>> > Clifton Park, NY 12065
>> > bill.hoff...@kitware.com
>> > http://www.kitware.com
>> > 518 881-4905 (Direct)
>> > 518 371-3971 x105
>> > Fax (518) 371-4573
>> > ___
>> > Powered by www.kitware.com
>> >
>> > Visit other Kitware open-source projects at
>> > http://www.kitware.com/opensource/opensource.html
>> >
>> > Please keep messages on-topic and check the CMake FAQ at:
>> > http://www.cmake.org/Wiki/CMake_FAQ
>> >
>> > Follow this link to subscribe/unsubscribe:
>> > http://www.cmake.org/mailman/listinfo/cmake
>> >
>>
>>
>>
>> --
>> Cheers,
>> Timothy St. Clair
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ExternalProject_Add + issues with env & auto-conf.
b4 I do this, because it's a non-trivial investment on a
non-heterogeneous build cluster, can you explain why the i386 stock
binaries behave differently?
Cheers,
Tim
On Tue, Oct 19, 2010 at 2:58 PM, Bill Hoffman wrote:
> Try the 2.8.3 release candidate.
>
> In 2.8.2 the untar did not preserve file times, and this could cause
> auto-make to rerun when it really did not need to.
>
> -Bill
>
>
> On 10/19/2010 3:21 PM, Tim St. Clair wrote:
>>
>> I've been able to consistently repro an issue using
>> ExternalProject_Add w/a configure build of cmake v.s. the i386
>> binaries online shows an issue whenever a it tries to call auto-conf
>> or auto-make as if the environment is hosed. When I use the stock
>> i386 binaries I do not see this issue and I'm able to build external
>> projects.
>>
>> The test example in question is the following:
>>
>>
>> set (LIBXML2_VER libxml2-2.7.3 )
>> ExternalProject_Add( libxml2
>> DEPENDS zlib
>> PREFIX
>> ${EXTERNAL_BUILD_PREFIX}/${LIBXML2_VER}
>> #-- Download Step --
>> DOWNLOAD_COMMAND wget -N
>> http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz ${CMD_TERM}
>> DOWNLOAD_DIR ${EXTERNAL_DL}
>> URL
>> http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz
>> #--Configure step --
>> CONFIGURE_COMMAND ./configure
>> --prefix=${EXTERNAL_STAGE}
>> --disable-shared --with-zlib=${EXTERNAL_STAGE}
>> #--Build Step --
>> BUILD_COMMAND make
>> BUILD_IN_SOURCE 1
>> #--install Step --
>> INSTALL_DIR ${EXTERNAL_STAGE}
>> INSTALL_COMMAND make install )
>
>
> --
> Bill Hoffman
> Kitware, Inc.
> 28 Corporate Drive
> Clifton Park, NY 12065
> bill.hoff...@kitware.com
> http://www.kitware.com
> 518 881-4905 (Direct)
> 518 371-3971 x105
> Fax (518) 371-4573
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] ExternalProject_Add + issues with env & auto-conf.
I've been able to consistently repro an issue using
ExternalProject_Add w/a configure build of cmake v.s. the i386
binaries online shows an issue whenever a it tries to call auto-conf
or auto-make as if the environment is hosed. When I use the stock
i386 binaries I do not see this issue and I'm able to build external
projects.
The test example in question is the following:
set (LIBXML2_VER libxml2-2.7.3 )
ExternalProject_Add( libxml2
DEPENDS zlib
PREFIX
${EXTERNAL_BUILD_PREFIX}/${LIBXML2_VER}
#-- Download Step --
DOWNLOAD_COMMAND wget -N
http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz ${CMD_TERM}
DOWNLOAD_DIR ${EXTERNAL_DL}
URL
http://parrot.cs.wisc.edu/externals/${LIBXML2_VER}.tar.gz
#--Configure step --
CONFIGURE_COMMAND ./configure
--prefix=${EXTERNAL_STAGE}
--disable-shared --with-zlib=${EXTERNAL_STAGE}
#--Build Step --
BUILD_COMMAND make
BUILD_IN_SOURCE 1
#--install Step --
INSTALL_DIR ${EXTERNAL_STAGE}
INSTALL_COMMAND make install )
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] listing of object file targets in an archive.
nevermind I've figured out a generic way to do what I need, build once and
link in multiple locations.
MACRO ( SRC_TARGET_REF _TARGET _REFS_EXPR _SRCREFS )
# 1st obtain the srcs
get_target_property ( _LSRCS ${_TARGET} SOURCES )
#loop through srouces and check matches
foreach ( _TARGET_SRC_FILE ${_LSRCS} )
#for each src file check all refs.
foreach ( _REF ${_REFS_EXPR} )
# if matches
if(${_TARGET_SRC_FILE} MATCHES ${_REF})
if(${_SRCREFS})
set (${_SRCREFS} "${${_SRCREFS}};${_TARGET_SRC_FILE}")
else(${_SRCREFS})
set (${_SRCREFS} ${_TARGET_SRC_FILE})
endif(${_SRCREFS})
endif()
endforeach( _REF )
endforeach( _TARGET_SRC_FILE )
ENDMACRO ( SRC_TARGET_REF )
## begin excerpt
src_target_ref( small_lib "^.*$" SMALL_LIB_REFS)
add_library( big_mundge_redistro_lib STATIC blah_blah.cpp;${SMALL_LIB_REFS}
)
add_dependencies (big_mundge_redistro_lib small_lib)
On Thu, Sep 9, 2010 at 11:19 AM, Tim St. Clair wrote:
> From within cmake I see a generation of the .o targets in my makefile, is
> there any way to get a listing without shelling out to ar?
>
> --
> Cheers,
> Timothy St. Clair
>
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Using objects in different targets
Sorry for my late weigh in on this one, but there are instances where this would be useful. E.g. redistro-ing libMyOneLargeLib.a which may be comprised of several other smaller libs. Basically I would like to build once, and pass the .o's into MyOneLargeLib. My only other alternative to add a custom build target to archive mundge, which is not a fun alternative. Cheers, Tim On Mon, May 24, 2010 at 4:12 AM, Alexander Neundorf wrote: > On Friday 21 May 2010, Christoph Rüdiger wrote: > > Am 20.05.2010 um 13:33 schrieb Michael Hertling: > > > On 05/20/2010 01:04 PM, "Christoph Rüdiger" wrote: > > >> [...] > > >> I've a directory src containing the complete source code of the > > >> program and > > >> another directory called test containing the source code for the > > >> unit tests. > > >> In the top level directory is a CMakeLists.txt that points to the > > >> subdirectories containing each an own CMakeLists.txt for building > > >> the program or the unit tests. > > >> > > >> Now I want to use the already build object files from the src > > >> directory one time for linking the program and one time for linking > > >> to the unit tests. > > >> > > >> My current way is building a static library in the src directory > > >> and link the unit tests against this library. But the sources would > > >> be compiled twice: One time for the static library and one time for > > >> the program itself. > > > > > > Link the program against the static library, too, while removing > > > the latter's source files from the program's ADD_EXECUTABLE(). > > > > Then I need either one big library which I can link against each unit > > test, resulting in a unit test of the size of the whole program plus > > the size of the unit test, > > A static library consists on UNIX just of a bunch of object files. > When linking a program against a static library, only those object files > will > be included in the resulting executable, which contain symbols which are > referenced. > So if your unit test uses only stuff from one object file (and this object > file doesn't use symbols from other object files in the static library), > only > this one object file will be included in the resulting executable. > > So, the unit tests shouldn't become too big. > > I guess it's somewhat similar under Windows. > > Alex > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] listing of object file targets in an archive.
>From within cmake I see a generation of the .o targets in my makefile, is there any way to get a listing without shelling out to ar? -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] adding prebuilt .o files to a cmake.a
For this chunk it only matters if I can decompose for *nix Makefiles.
Cheers,
Tim
On Thu, Sep 9, 2010 at 7:41 AM, David Cole wrote:
> To the best of my knowledge, there is not an easy, cross-platform way to
> decompose.
>
>
>
> On Wed, Sep 8, 2010 at 11:43 PM, Tim St. Clair wrote:
>
>> I guess a follow on to that would be the opposite to composition. If I
>> wanted to decompose a cmake library to determine what object files it
>> contains is there an easy mechanism for this?
>>
>> Cheers,
>> Tim
>>
>>
>> On Wed, Sep 8, 2010 at 4:30 PM, David Cole wrote:
>>
>>> On Wed, Sep 8, 2010 at 4:54 PM, Tim St. Clair wrote:
>>>
>>>> Folks,
>>>>
>>>> Is there an easy way (best practice) to add prebuilt .o files
>>>> (external to my build) to a .a easily?
>>>>
>>>> --
>>>> Cheers,
>>>> Timothy St. Clair
>>>>
>>>>
>>>> ___
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at
>>>> http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Please keep messages on-topic and check the CMake FAQ at:
>>>> http://www.cmake.org/Wiki/CMake_FAQ
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://www.cmake.org/mailman/listinfo/cmake
>>>>
>>>
>>> If it's compatible with the other .o files being built to go in your
>>> library, just add the .o file in question as a "source file":
>>>
>>> add_library(mylib /path/to/my.o ${other_sources})
>>>
>>>
>>> HTH,
>>> David
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Timothy St. Clair
>>
>>
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] adding prebuilt .o files to a cmake.a
I guess a follow on to that would be the opposite to composition. If I
wanted to decompose a cmake library to determine what object files it
contains is there an easy mechanism for this?
Cheers,
Tim
On Wed, Sep 8, 2010 at 4:30 PM, David Cole wrote:
> On Wed, Sep 8, 2010 at 4:54 PM, Tim St. Clair wrote:
>
>> Folks,
>>
>> Is there an easy way (best practice) to add prebuilt .o files
>> (external to my build) to a .a easily?
>>
>> --
>> Cheers,
>> Timothy St. Clair
>>
>>
>> ___
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Please keep messages on-topic and check the CMake FAQ at:
>> http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.cmake.org/mailman/listinfo/cmake
>>
>
> If it's compatible with the other .o files being built to go in your
> library, just add the .o file in question as a "source file":
>
> add_library(mylib /path/to/my.o ${other_sources})
>
>
> HTH,
> David
>
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] adding prebuilt .o files to a cmake.a
Folks, Is there an easy way (best practice) to add prebuilt .o files (external to my build) to a .a easily? -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] detecting libc version info
Phil - Thanks for the feedback, I was able to create a macro which uses try_run to detect. Cheers, Tim On Tue, Aug 31, 2010 at 11:05 PM, Philip Lowman wrote: > On Tue, Aug 31, 2010 at 3:01 PM, Tim St. Clair wrote: > >> Is there a handy dandy marco for detecting libc details (e.g. version). > > > Probably not. You can use preprocessor checks though. > > glibc: > http://predef.sourceforge.net/prelib.html#sec3 > > gcc: > http://predef.sourceforge.net/precomp.html#sec15 > > HTH > > -- > Philip Lowman > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] detecting libc version info
Is there a handy dandy marco for detecting libc details (e.g. version). -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] cmake -E tar on Darwin 10.4
Folks - I'm running cmake 2.8.0 and noticing an interesting anomaly on Darwin 10.4 when extracting an external project: cmake -E tar xfz globus-5.0.1.tar.gz CMake Error: Problem with tar_extract_all(): Operation not permitted CMake Error: Problem extracting tar: globus-5.0.1.tar.gz yet, tar -xzf globus-5.0.1.tar.gz works fine. are there any known issues that I'm not aware of? -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] random failures on windows INSTALL target. "file INSTALL cannot copy file"
1-more point, when I check, the file is actually copied. On Wed, Feb 24, 2010 at 3:51 PM, Tim St. Clair wrote: > I've been noticing random failures on file copy operations of install > targets when they are copying a lot of files. (e.g. - headers for a > install library) > > "file INSTALL cannot copy file" > > I've verified there is nothing in the way, and I'm uncertain what the > actual error is. > It's intermittent and only happens when copying a large number of files. > > Is there a timeout parameter I can set. > > -- > Cheers, > Timothy St. Clair > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] random failures on windows INSTALL target. "file INSTALL cannot copy file"
I've been noticing random failures on file copy operations of install targets when they are copying a lot of files. (e.g. - headers for a install library) "file INSTALL cannot copy file" I've verified there is nothing in the way, and I'm uncertain what the actual error is. It's intermittent and only happens when copying a large number of files. Is there a timeout parameter I can set. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] copy on install
Response Below
Inline...
On Fri, Feb 5, 2010 at 12:05 AM, Alan W. Irwin
wrote:
> On 2010-02-04 22:44-0600 Tim St. Clair wrote:
>>
>> On Thu, Feb 4, 2010 at 6:14 PM, Alan W. Irwin
>> wrote:
>>>
>>> Why not simply use install(FILES ... PERMISSIONS RENAME ... )?
>>>
>>> You would have to use the target property LOCATION to find the
>>> (cross-platform) filename associated with the target, and you would have
>>> to
>>> specify the appropriate PERMISSIONS, but I think this method of using
>>> install(FILES ...) should work fine unless and until a feature request
>>> for a
>>> RENAME option for install(TARGETS) is implemented.
>>>
>>
>> I like this solution however when I try it... it does not expand the
>> $(OutDir) which was yielded when I called get_target_property
>> w/LOCATION.
>
> I have never had trouble with the LOCATION property. I use it as follows:
>
> get_target_property(variable_name target_name LOCATION)
> message(STATUS "variable_name=${variable_name}")
>
> which outputs the full path name of the target. Don't you get that?
>
Yup, on windows LOCATION output =
c:\My_Src_Path\$(OutDir)\my_target.exe
I was thinking about using ${CMAKE_BUILD_TYPE}_LOCATION($(OutDir) =
Release, Debug...) but on windows there is no guarantee that will be
the default config, and when you change build configurations your
install and package targets will light on fire because they are pin'd
to a certain config.
For the time being I have just duplicated the targets (which is
non-ideal) as it increases the build time. I'm thinking this is a
limitation in CMAKE. It would be nice if you could have aliases for
install targets which would copy on windows, and soflink &&|| copy on
*nix.
Cheers,
Tim
> Alan
> __
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state implementation
> for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
> package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
> Linux Links project (loll.sf.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __
>
> Linux-powered Science
> __
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] copy on install
Inline.. Re: Alan
On Thu, Feb 4, 2010 at 6:14 PM, Alan W. Irwin wrote:
> On 2010-02-04 23:38+0100 Eric Noulard wrote:
>
>> 2010/2/4 Tim St. Clair :
>>>
>>> Is there a clean way to copy the install target e.g.
>>>
>>> install (TARGETS foo DESTINATION bin)
>>>
>>> ~ install(TARGETS foo DESTINATION loc2 RENAME foo_bar) <-doesn't exist.
>>>
>>> I basically need to install the same target to *multiple* locations
>>> with different names.
>>
>> I think multiple location is already supported just call
>>
>> install (TARGETS foo DESTINATION loc1)
>> install (TARGETS foo DESTINATION loc2)
>> install (TARGETS foo DESTINATION loc3)
>> etc...
>>
>> now concerning renaming without building the same target several times?
>> May be with add_custom_command
>>
>> add_custom_command(TARGET foo
>> POST_BUILD
>> COMMAND ${CMAKE_COMMAND} -E copy
>> foo ${CMAKE_BINARY_DIR}/foo_renamed)
>>
>> +
>> install(FILES ${CMAKE_BINARY_DIR}/foo_renamed DESTINATION loc2)
>>
>>
>> this may not really solves the problem because install(FILES djfldfj)
>> won't make what install(TARGETS do like rpath handling etc
>>
>> a working (but ugly solution) would be to built the target as many
>> time as you need to with the needed different name each time.
>
> Why not simply use install(FILES ... PERMISSIONS RENAME ... )?
>
> You would have to use the target property LOCATION to find the
> (cross-platform) filename associated with the target, and you would have to
> specify the appropriate PERMISSIONS, but I think this method of using
> install(FILES ...) should work fine unless and until a feature request for a
> RENAME option for install(TARGETS) is implemented.
>
I like this solution however when I try it... it does not expand the
$(OutDir) which was yielded when I called get_target_property
w/LOCATION. The only other option I can think of is to use a post
install script.
> Alan
> __
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state implementation
> for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
> package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
> Linux Links project (loll.sf.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __
>
> Linux-powered Science
> __
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] copy on install
Is there a clean way to copy the install target e.g. install (TARGETS foo DESTINATION bin) ~ install(TARGETS foo DESTINATION loc2 RENAME foo_bar) <-doesn't exist. I basically need to install the same target to *multiple* locations with different names. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] C++/CLI projects
Folks - Is there a way to create Managed C++ project files and specify all the properties? I've been googling but I haven't found much, if needed I will resort to include_external_msproject(). -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack WiX patch
Inline... On Mon, Feb 1, 2010 at 11:43 AM, Bill Hoffman wrote: > Tim St. Clair wrote: > >>> Do you think we could use configure_file to create the .xml file like we >>> do >>> with the NSIS generator? >> >> That is exactly what I do, but I do it prior to cpack running, but in >> this case it would have to be a .xsl. >> >> It would be best if this installer could use the >>> >>> standards set of CPACK_* variables to create an installer. I maybe >>> reading >>> your code wrong, but I think the only thing that it is used is the list >>> of >>> sources. >>> >> >> I had planned on letting the user control their .xsl and minimizing >> the number of variables, as you can only automate so much, but I will >> let others decide. > > It should just "work" by default with the usual CPACK variables. The > variables are sufficient to get a basic NSIS installer working. They should > be enough for WiX. If people want to do further customization they can > always override the template file used by CPack. That should be easy enough to auto-gen a .xsl by default. It would go into CPackWIX.cmake which should not affect the mainline src. If I get some time this week I will try to update. >> >> Right now it's a first start and should be able to get folks rolling. >> >>> For example, what to you get if you try to package Tutorial/Step7 with >>> the >>> WiX CPack generator? >>> >> >> I may take a look later, I have to finish my installer ;-) >> > > OK. > > -Bill > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CPack WiX patch
Inline.. On Mon, Feb 1, 2010 at 10:36 AM, Bill Hoffman wrote: > Tim St. Clair wrote: >> >> CMake Community - >> >> I've created a patch for CPack to incorporate WiX (to create .msi's), >> patch and info can be found @ >> >> http://annealingtechnologies.blogspot.com/2010/02/wix-and-cpack-integration.html >> >> I pass the baton for others to push upstream. >> > This looks promising, thanks! > > Do you think we could use configure_file to create the .xml file like we do > with the NSIS generator? That is exactly what I do, but I do it prior to cpack running, but in this case it would have to be a .xsl. It would be best if this installer could use the > standards set of CPACK_* variables to create an installer. I maybe reading > your code wrong, but I think the only thing that it is used is the list of > sources. > I had planned on letting the user control their .xsl and minimizing the number of variables, as you can only automate so much, but I will let others decide. Right now it's a first start and should be able to get folks rolling. > For example, what to you get if you try to package Tutorial/Step7 with the > WiX CPack generator? > I may take a look later, I have to finish my installer ;-) > > > -Bill > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack WiX patch
CMake Community - I've created a patch for CPack to incorporate WiX (to create .msi's), patch and info can be found @ http://annealingtechnologies.blogspot.com/2010/02/wix-and-cpack-integration.html I pass the baton for others to push upstream. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Planned release of 2.8.1?
When is the planned release of 2.8.1? Is there a online roadmap? -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] ExternalProject_Add inserting " around *'s "
I found the source of the error:
ExternalProject.cmake (line 583)
add_custom_command(
OUTPUT ${stamp_dir}${cfgdir}/${name}-${step}
COMMENT ${comment}
COMMAND ${command}
COMMAND ${touch}
DEPENDS ${depends}
WORKING_DIRECTORY ${work_dir}
VERBATIM
)
nix VERBATIM, and all is well
Hope this helps others from wasting hours of their life as I have.
Cheers,
Tim
On Thu, Jan 7, 2010 at 10:45 PM, Tim St. Clair wrote:
> For whatever command I am using if I insert a wild card to be passed in e.g.
>
> INSTALL_COMMAND cp blah/* ${MY_STAGING}
>
> becomes cp "blah/*"
>
> which will then yield an error.
>
> Is there some escape sequence I'm missing to avoid the quoting?
>
> --
> Cheers,
> Timothy St. Clair
>
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] Quoting of commands.
Is there a global way to disable all CMake quoting of commands? It appears that CMake is parsing some commands and inserting quotes in places and it is causing me much grief. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] ExternalProject_Add inserting " around *'s "
For whatever command I am using if I insert a wild card to be passed in e.g.
INSTALL_COMMAND cp blah/* ${MY_STAGING}
becomes cp "blah/*"
which will then yield an error.
Is there some escape sequence I'm missing to avoid the quoting?
--
Cheers,
Timothy St. Clair
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Build only what you need in third party libs
Watch out gentoo, and buildroot, here comes cmake ;-) I just tested and it works like a charm, nice job! just as a side note for other users, make certain you don't "quote" your commands. Cheers, Tim On Tue, Dec 22, 2009 at 8:50 AM, David Cole wrote: > On Tue, Dec 22, 2009 at 9:37 AM, Troy D. Straszheim > wrote: >> >> David Cole writes: >> >> > On Tue, Dec 22, 2009 at 7:58 AM, David Wolfe >> > wrote: >> > >> > On 12/22/2009 7:11 AM, David Wolfe wrote: >> > >> > Most of our external >> > dependencies aren't even built using CMake, so 'CMake-ifying' >> > everything >> > under one big über-build hardly seems worth it... >> > >> > >> > On 12/22/2009 6:50 AM, David Cole wrote: >> > >> > One way to overcome these things, but still build projects from >> > source >> > code as needed is to use a new feature in CMake 2.8: the >> > ExternalProject >> > module... >> > >> > >> > Wow. That could be *really* useful---especially the fact that it >> > allows >> > you to download sources from the web, CVS, svn, etc. It might be >> > enough >> > to change my mind about maintaining a separate externals archive. >> > :-) >> > >> > >> > >> > If it's not enough to change your mind.. let me know what you think >> > it's >> > missing. >> > >> >> Here's a use-case: boost-cmake exports buildspace targets to >> $CMAKE_BINARY_DIR/lib/Exports.cmake. So you'd want to download, >> extract, run cmake on the unpacked archive, and only then include() the >> exported targets... Does ExternalProject work this way? > > It does work that way if you set it up that way. > So you would have one ExternalProject_Add call to build and install > boost-cmake... and then a subsequent ExternalProject_Add call to build > something that depends on it. In this dependent project you would use > "DEPENDS boost-cmake-proj" to express this dependency. And pass whatever -D > or prefix information you need to the configure step of this dependent > project so that it knows where the boost-cmake build is. > An external project must configure, build and install all the way before any > of the projects that depend on it even run their first build step. > It's pretty flexible and customizable. If there's a build step that does not > do what you want it to by default, you can replace it with your own custom > step. And you can inject custom steps into the stream of steps that occur by > default, too. > HTH, > David > > ___ > Powered by www.kitware.com > > Visit other Kitware open-source projects at > http://www.kitware.com/opensource/opensource.html > > Please keep messages on-topic and check the CMake FAQ at: > http://www.cmake.org/Wiki/CMake_FAQ > > Follow this link to subscribe/unsubscribe: > http://www.cmake.org/mailman/listinfo/cmake > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Cannot find source file.
I would contend that this should be a warning vs. an error, which prevents generation. Cheers, Tim On Thu, Dec 10, 2009 at 3:18 PM, Alexander Neundorf wrote: > On Thursday 10 December 2009, Tyler Roscoe wrote: >> On Thu, Dec 10, 2009 at 02:14:28PM -0600, Tim St. Clair wrote: >> > Do all files *have* to be present during generation? Or is there some >> > lazy evaluation? >> >> Look at the GENERATED property for source files. >> >> > The file it is looking for is one of many gen'd files. It would be a >> > pain if I had to update all the command outputs in order to create the >> > deps. >> >> Having well-constructed links between command outputs and dependencies >> sounds like a really good idea to me. > > Yes, it's even necessary. If your add_custom_commands() don't list all the > files they generate and if not all generated files are listed as sources for > the target which needs them then the dependencies will be incomplete, and > builds (or at least parallel builds) will break. > > Alex > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CPack & WiX
I was just wondering if anyone has created a WiX cpack-generator yet, the wiki says "no", but the wiki is stale and I'm rather surprised that no one has done it. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Cannot find source file.
Do all files *have* to be present during generation? Or is there some lazy evaluation? The file it is looking for is one of many gen'd files. It would be a pain if I had to update all the command outputs in order to create the deps. -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMAKE vsprops or equivalent...
I figured I would tickle this again, b/c it seemed like you knew a solution... Cheers, Tim On Wed, Dec 9, 2009 at 12:01 PM, Tim St. Clair wrote: > Environment variable, for the exact reason you mentioned. > > On Wed, Dec 9, 2009 at 11:23 AM, Mike Jackson > wrote: >> On Wed, Dec 9, 2009 at 12:09 PM, Tim St. Clair wrote: >>> when using vsprops on windows, you can set environment variables which >>> will be exist for a given project when it compiles. >>> >>> The example given in the link below: >>> set_tests_properties(SomeTest PROPERTIES ENVIRONMENT >>> "PATH=c:\somedir;c:\otherdir") >>> >>> is close to what I'm looking for, but I would like it to be fore any >>> TARGET. I tried doing: >>> set_properties(MyTarget PROPERTIES ENVIRONMENT "MYVAR=foo1;MYVAR2=foo2") >>> with no success on visual studio 2008. During compilation of MyTarget >>> those vars *do not* appear to be set. >>> >>> The template .vcproj, is kinda ugly, but may be last hope unless there >>> is a cleaner method for doing thing in VS. >>> >>> Cheers, >>> Tim >>> >>> >>> On Wed, Dec 9, 2009 at 10:54 AM, Tyler Roscoe wrote: >>>> On Wed, Dec 09, 2009 at 07:49:12AM -0600, Tim St. Clair wrote: >>>>> Is there support for visual studio property sheets in CMAKE, or the >>>>> equivalent for *compile-time* env settings? >>>> >>>> I haven't played with this solution but maybe it will help: >>>> >>>> http://stackoverflow.com/questions/1005901/how-to-set-path-environment-variable-using-cmake-and-visual-studio-to-run-test >>>> >>>> I don't know what you mean by "compile-time env settings". >>>> >>>>> I have had little luck finding this information online, and there are >>>>> no (+,-) refs in the manual. >>>> >>>> I don't know what you mean by "(+,-) refs in the manual". >>>> >>>> tyler >>>> >>> >>> >>> >>> -- >>> Cheers, >>> Timothy St. Clair >> >> >> Little late to the thread, but are you trying to set a Compile >> Definition on an actual environment variable because a script or >> something else is running during the compilation and it needs to know >> where/what something is? >> >> _ >> Mike Jackson mike.jack...@bluequartz.net >> BlueQuartz Software www.bluequartz.net >> Principal Software Engineer Dayton, Ohio >> > > > > -- > Cheers, > Timothy St. Clair > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMAKE vsprops or equivalent...
Environment variable, for the exact reason you mentioned. On Wed, Dec 9, 2009 at 11:23 AM, Mike Jackson wrote: > On Wed, Dec 9, 2009 at 12:09 PM, Tim St. Clair wrote: >> when using vsprops on windows, you can set environment variables which >> will be exist for a given project when it compiles. >> >> The example given in the link below: >> set_tests_properties(SomeTest PROPERTIES ENVIRONMENT >> "PATH=c:\somedir;c:\otherdir") >> >> is close to what I'm looking for, but I would like it to be fore any >> TARGET. I tried doing: >> set_properties(MyTarget PROPERTIES ENVIRONMENT "MYVAR=foo1;MYVAR2=foo2") >> with no success on visual studio 2008. During compilation of MyTarget >> those vars *do not* appear to be set. >> >> The template .vcproj, is kinda ugly, but may be last hope unless there >> is a cleaner method for doing thing in VS. >> >> Cheers, >> Tim >> >> >> On Wed, Dec 9, 2009 at 10:54 AM, Tyler Roscoe wrote: >>> On Wed, Dec 09, 2009 at 07:49:12AM -0600, Tim St. Clair wrote: >>>> Is there support for visual studio property sheets in CMAKE, or the >>>> equivalent for *compile-time* env settings? >>> >>> I haven't played with this solution but maybe it will help: >>> >>> http://stackoverflow.com/questions/1005901/how-to-set-path-environment-variable-using-cmake-and-visual-studio-to-run-test >>> >>> I don't know what you mean by "compile-time env settings". >>> >>>> I have had little luck finding this information online, and there are >>>> no (+,-) refs in the manual. >>> >>> I don't know what you mean by "(+,-) refs in the manual". >>> >>> tyler >>> >> >> >> >> -- >> Cheers, >> Timothy St. Clair > > > Little late to the thread, but are you trying to set a Compile > Definition on an actual environment variable because a script or > something else is running during the compilation and it needs to know > where/what something is? > > _ > Mike Jackson mike.jack...@bluequartz.net > BlueQuartz Software www.bluequartz.net > Principal Software Engineer Dayton, Ohio > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] CMAKE vsprops or equivalent...
when using vsprops on windows, you can set environment variables which will be exist for a given project when it compiles. The example given in the link below: set_tests_properties(SomeTest PROPERTIES ENVIRONMENT "PATH=c:\somedir;c:\otherdir") is close to what I'm looking for, but I would like it to be fore any TARGET. I tried doing: set_properties(MyTarget PROPERTIES ENVIRONMENT "MYVAR=foo1;MYVAR2=foo2") with no success on visual studio 2008. During compilation of MyTarget those vars *do not* appear to be set. The template .vcproj, is kinda ugly, but may be last hope unless there is a cleaner method for doing thing in VS. Cheers, Tim On Wed, Dec 9, 2009 at 10:54 AM, Tyler Roscoe wrote: > On Wed, Dec 09, 2009 at 07:49:12AM -0600, Tim St. Clair wrote: >> Is there support for visual studio property sheets in CMAKE, or the >> equivalent for *compile-time* env settings? > > I haven't played with this solution but maybe it will help: > > http://stackoverflow.com/questions/1005901/how-to-set-path-environment-variable-using-cmake-and-visual-studio-to-run-test > > I don't know what you mean by "compile-time env settings". > >> I have had little luck finding this information online, and there are >> no (+,-) refs in the manual. > > I don't know what you mean by "(+,-) refs in the manual". > > tyler > -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] CMAKE vsprops or equivalent...
Is there support for visual studio property sheets in CMAKE, or the equivalent for *compile-time* env settings? I need this for projects which call out to legacy scripts which require those vars during compilation. I have had little luck finding this information online, and there are no (+,-) refs in the manual. Also, if this support does not exist yet is there a plan to add it? -- Cheers, Timothy St. Clair ___ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
