Sorry to bump this, but I would really like some feedback on either I'm
being wrong or correct on these points?
Thanks for your time.
Joel Lamotte
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages o
On Mon, Oct 22, 2012 at 5:55 PM, David Cole wrote:
> On Mon, Oct 22, 2012 at 6:38 AM, Arindam Mukherjee
> wrote:
>> On Mon, Oct 22, 2012 at 4:06 PM, Arindam Mukherjee
>> wrote:
>>> I am sorry I missed your response. Here are the details:
>>>
>>> 1. I have a shell / batch script which does two th
On 2012-10-24 10:35, DavidAllen wrote:
I am currently looking at replacing my unix makefile (linux+gmake,
solaris+make/gmake) and Windows VS projects, with cmake.
For the makefiles I get gcc to output dependency files based on header file
usage, using gcc options -MM -MF -MP -MT.
This has worke
Matthew Woehlke writes:
> I'm not sure that's correct behavior. What if the modification to the
> .cpp file was to remove the definition of a function declared in a
> header? Now your executable that was using that function will crash when
> you try to run it due to a missing symbol. If you h
On 10/25/2012 1:17 PM, Leif Walsh wrote:
Yes, but this is a very rare thing to do. And the "failure" result is
just that the problem would be discovered at test time instead of link
time.
What's being proposed here is a massive optimization for the common case
(changing code in a library and no
Is there anything that would convince kitware that the behavior I describe is
worth pursuing, even as a non-default option? I'd implement it myself but your
code is foreign to me and I bet someone at kitware knows the exact line that
needs to change to enable this.
The reason I'm pushing so ha
I can't see why you couldn't use set(CMAKE_SKIP_RPATH ON) and post
build copy your library to a path that's on your linker path; have
your tests setup to use the system copy of the library instead of the
local copy.
~
Doug.
On Sat, Aug 4, 2012 at 2:41 AM, Leif Walsh wrote:
> This is sort of the
Because that doesn't retain the dependencies that do the linking the first time
around. It's also messy and non-portable.
Sent from my iPhone
On Oct 25, 2012, at 21:52, Doug wrote:
> I can't see why you couldn't use set(CMAKE_SKIP_RPATH ON) and post
> build copy your library to a path that's
