On 07/22/2010 09:18 AM, Alan W. Irwin wrote:
> On 2010-07-22 03:09+0200 Michael Hertling wrote:
>
>> In summary, my point is: Even if the loops are swapped, we wouldn't get
>> a solution that works well in real-world scenarios so I doubt if it's
>> worth the effort [...].
>
> Hi Michael:
>
> I t
On 07/22/2010 01:30 PM, Michael Wild wrote:
> Thanks for reminding me of my old idea ;-)
> http://www.cmake.org/pipermail/cmake/2010-May/036993.html
>
> I think that would be the cleanest solution. Extract the loop body into a
> function and then have two separate loops calling the same function
I¹m not using any External Projects (#10735), but I can see that its
somewhat similar.
Although bizzaringly this appears to be a single file (so far) in one
target, the single CMakeLists file is ~100k with ~20 targets, and its
successfully built the rest of Poco (and my own stuff).
I¹ll make th
Possibly related to these bugs...?
http://public.kitware.com/Bug/view.php?id=9963
http://public.kitware.com/Bug/view.php?id=10735
This is just a guess because the symptom sounds similar...
To confirm (or deny) can you send along a zip file of a project that
demonstrates the problem?
Does the pr
On Sun, Aug 1, 2010 at 6:17 PM, Eric Noulard wrote:
> 2010/8/1 Dennis Schridde :
> > Hello!
> >
> > I just started experimenting with CPack. According to the docs and
> > code it is to be used like this:
> >> set(CPACK_... ...)
> >>
> > include(CPack)
> >
> > This, however, does not allow making
On 2010-08-01, Alexander Neundorf wrote:
> > Hi, I've done some googling but came up with nothing
> > so just wondering if anyone here knows of a tool to
> > convert python waf based projects to Cmake?
>
> I don't think so, waf is not too widespread AFAIK.
Sorry to ask such a naive question but i
One of my libraries has started to fail to link due to unresolved symbols,
because the TCPServerDispatcher class is not being linked. It is in fact not
even being compiled.
Its not mentioned even in the generated NMakefile.
I¹ve deleted the entire build directory and rebuilt from scratch with
2010/8/1 Dennis Schridde :
> Hello!
>
> I just started experimenting with CPack. According to the docs and
> code it is to be used like this:
>> set(CPACK_... ...)
>>
> include(CPack)
>
> This, however, does not allow making use of the defaults
> present in CPack.cmake. (Most notably CPACK_SOURCE_I
On Sunday 01 August 2010, Dennis Schridde wrote:
> Hello!
>
> The binary I am building has a dependency on an external
> library.
> This library may be present system-wide, otherwise I am building it
> in a subdirectory.
> Therefore I am calling these
> commands:
>
> add_custom_target(BuildMyLib ..
On Sunday 01 August 2010, Mark Constable wrote:
> Hi, I've done some googling but came up with nothing
> so just wondering if anyone here knows of a tool to
> convert python waf based projects to Cmake?
I don't think so, waf is not too widespread AFAIK.
Alex
__
Hello!
I just started experimenting with CPack. According to the docs and
code it is to be used like this:
> set(CPACK_... ...)
>
include(CPack)
This, however, does not allow making use of the defaults
present in CPack.cmake. (Most notably CPACK_SOURCE_IGNORE_FILES.)
I had to
copy the default val
I just notice that this command does not do what I expected it to do:
>
set_property(TARGET MyLib PROPERTY IMPORTED_LOCATION
"${MYLIB_DIR}/build")
Apparently it sets the path to the *file* that is
MyLib, not to the directory it is in. Is there a property to set the path to
the *directory*?
With CM
Hello!
The binary I am building has a dependency on an external
library.
This library may be present system-wide, otherwise I am building it
in a subdirectory.
Therefore I am calling these
commands:
add_custom_target(BuildMyLib ...)
add_library(MyLib SHARED
IMPORTED)
add_dependencies(MyLib BuildM
13 matches
Mail list logo
