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
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,
>
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,
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
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,
T
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
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?
>>
n 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?
>>
&g
d 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 b
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 ab
_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
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 c
>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.ki
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. C
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
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/
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 (
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-
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
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)
>
&
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
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 RENAM
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 fo
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
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.kitwar
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 p
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://a
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
_
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 a
, 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}
>
> b
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 Kitw
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
___
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.
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:
>>
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-sourc
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
_
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,
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 w
st 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
>> equivalen
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 (+,-) ref
40 matches
Mail list logo