L.M. de Vries wrote:
Hi,
Just confirming that this problem is solved with RC4.
Yes, it should be.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep mess
On Wednesday 28 October 2009, Dixon, Shane wrote:
> The error message I get if I don't force the compiler is this:
>
> http://pastebin.com/m185e1316
So "gcc-fm.exe main.c -rdynamic" fails ?
Does "gcc-fm.exe main.c -shared" work ?
> The paths are:
> C:\Program Files\Eracom\ProtectProcessing Ora
Hi,
Just confirming that this problem is solved with RC4.
Thanks,
Luis
___
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 FA
The error message I get if I don't force the compiler is this:
http://pastebin.com/m185e1316
The paths are:
C:\Program Files\Eracom\ProtectProcessing Orange SDK\lib\armfm\libfmcrt.a
C:\Program Files\Eracom\ProtectToolkit C SDK\include\cryptoki.h
Ah, just in pasting that I see part of the proble
Hi,
On Wednesday 28 October 2009, Dixon, Shane wrote:
> I'm using a toolchain.cmake file (see below). I then try to find a library
> after loading this toolchain (using -DCMAKE_TOOLCHAIN_FILE=... Option). I
> can't find the library regardless of how I set the CMAKE_FIND_ROOT_PATH
> settings. I
Okay, so a little more digging and I have a bit more information. I tried
find_path() and that one fails until I add "NO_CMAKE_FIND_ROOT_PATH" and then
it finds the files just fine. It just seems like find_library() that's not
respecting the "NO_CMAKE_FIND_ROOT_PATH".
#works
FIND_PATH( ERACO
I'm using a toolchain.cmake file (see below). I then try to find a library
after loading this toolchain (using -DCMAKE_TOOLCHAIN_FILE=... Option). I
can't find the library regardless of how I set the CMAKE_FIND_ROOT_PATH
settings. I try setting it to NO and still can't find the library.
It's
On Wed, Oct 28, 2009 at 02:32:22PM -0400, David Cole wrote:
> You are touching an existing header file...
>
> What happens if you add a new header file that was not there the first time
> you ran make install?
Sorry, I left out the part where I cleaned up and switched to the other
CMakeLists in my
Actually, never mind. bar.h was a new header file, wasn't it?
The difference then is that install(DIRECTORY always scans the entire
directory structure and copies new stuff in when it appears. Seems odd to
add a header file and then not have to build anything before doing another
make install... b
You are touching an existing header file...
What happens if you add a new header file that was not there the first time
you ran make install?
On Wed, Oct 28, 2009 at 2:26 PM, Tyler Roscoe wrote:
> On Wed, Oct 28, 2009 at 01:18:55PM -0400, David Cole wrote:
> > Except: that argument is not vali
On Wed, Oct 28, 2009 at 01:18:55PM -0400, David Cole wrote:
> Except: that argument is not valid in this case. Neither file(GLOB nor
> install(DIRECTORY will "rerun" anything if a new header file is added into
> the directory...
David I don't think this is correct.
Here's a test using file(GLOB)
In CVS CMake and in the new 2.8 RC 4, there is a new module called:
CMakeVerifyManifest.cmake.
To run it, cd into the binary install directory for your project and run
cmake -P /path/to/CMakeVerifyManifest.cmake. It will check dll and exe
files for embedded manifests and make sure they match
CMake 2.8.0 RC 4 is now ready for people to try.
You can find the source and binaries here: http://www.cmake.org/files/v2.8/.
Here are the changes for the 2.8.0 branch so far:
Changes in CMake 2.8.0 RC 4
- Fix try_compile when file cannot be found
- Add new module to test manifest installation is
On Wed, Oct 28, 2009 at 11:45 AM, Mathieu Malaterre <
mathieu.malate...@gmail.com> wrote:
> On Wed, Oct 28, 2009 at 4:41 PM, Tyler Roscoe wrote:
> > This is a bad practice because then CMake has no way to know if there
> > are new header files and can't regenerate/install correctly. Ok maybe a
>
On Tue, October 27, 2009 2:15 pm, Werner Smekal wrote:
> Hi Orion,
>
> On Oct 27, 2009, at 6:53 PM, Orion Poplawski wrote:
>
>> On 10/26/2009 12:44 PM, Orion Poplawski wrote:
>>> in 2.8.0, FindwxWidgets.cmake strips -D from
>>> wxWidgets_DEFINITIONS. Why?
>>>
>>
>> Note that this is breaking prev
Initial tests show that 2.9 20091027 does indeed fix the problem. I had
added in some attempts at working around the problem, which I reverted
for this test, and cmake worked as desired (it used to rebuild every
time). I'll continue development and let you know if I see it occur again.
A big
On Wed, Oct 28, 2009 at 4:41 PM, Tyler Roscoe wrote:
> This is a bad practice because then CMake has no way to know if there
> are new header files and can't regenerate/install correctly. Ok maybe a
> new header coming in will happen to trigger a rerun of CMake because the
> header happens to belo
On Wed, Oct 28, 2009 at 04:28:51PM +0100, Mathieu Malaterre wrote:
> I do not understand why I need to explicitely state
>
> PATTERN ".svn" EXCLUDE
>
> (what if tomorrow I switch to CVS, git, or mercurial), so I reverted
Then you use 'PATTERN "${my_vcs_dir}" EXCLUDE' instead.
> file(GLOB head
Kevin Burge wrote:
I neglected to mention that the same cmake files do not do this on the
same release of cmake on Linux, Solaris or AIX
I am pretty sure this is the same issue as the ZERO_CHECK problem that
has been on the list. Can you try the nightly version 2.9 Oct 27 and
see if it fix
On Wed, Oct 28, 2009 at 4:14 PM, Steve Huston wrote:
> Hi Mathieu,
>
>> Quick question. What is the command to install a set of *.h files
> ?
>>
>> I tried:
>>
>> install(DIRECTORY . DESTINATION include/proj FILES_MATCHING
>> PATTERN "*.h")
>
> Right.
>
>> but it is installing the '.svn' subdir
I neglected to mention that the same cmake files do not do this on the
same release of cmake on Linux, Solaris or AIX
Kevin Burge wrote:
I'm having a problem where I make some change to one of the
CMakeLists.txt file in the root of a large tree of projects and on
windows...
__
I'm having a problem where I make some change to one of the
CMakeLists.txt file in the root of a large tree of projects and on
windows, when the configure/generate stage is done, it wipes out all the
stamp files and directories created by add_custom_command, and basically
rebuilds everything.
On Wed, Oct 28, 2009 at 09:02:52AM +0100, Dietmar Hummel wrote:
> What I would like to handle are targets like
> release
> debug
> demo release (additionals defines)
> first customer oem release (other additional defines)
> second customer oem release (again different set of defines)
> ... and so o
Hi Mathieu,
> Quick question. What is the command to install a set of *.h files
?
>
> I tried:
>
> install(DIRECTORY . DESTINATION include/proj FILES_MATCHING
> PATTERN "*.h")
Right.
> but it is installing the '.svn' subdir as part of the installation.
Try adding:
PATTERN ".svn"
On Wed, Oct 28, 2009 at 02:49:25PM +0100, Mathieu Malaterre wrote:
> install(DIRECTORY . DESTINATION include/proj FILES_MATCHING PATTERN "*.h")
>
> but it is installing the '.svn' subdir as part of the installation.
Is it creating .svn but not putting any files in it (unless they match
*.h, which
Hum, let's try again. I'd like to know if there is an API to query
properties of 'mylib-targets' as in:
add_library(mylib SHARED mylib.c mylib.h)
add_library(mylib2 SHARED mylib.c mylib.h)
install(TARGETS mylib mylib2 DESTINATION lib/myproj EXPORT mylib-targets)
install(EXPORT mylib-targets DESTIN
Hi there,
Quick question. What is the command to install a set of *.h files ?
I tried:
install(DIRECTORY . DESTINATION include/proj FILES_MATCHING PATTERN "*.h")
but it is installing the '.svn' subdir as part of the installation.
Thanks,
--
Mathieu
__
Ah yes, you are right.
Thanks for explaining...and sorry for noise. :-)
Greetings,
LM
Marcel Loose wrote:
Hi Luis,
The way I'm reading the globbing expression -- which is not identical to
a regex, BTW -- the output makes perfect sense.
In HDR1 you collect all filenames that start with 'Spati
Hi Luis,
The way I'm reading the globbing expression -- which is not identical to
a regex, BTW -- the output makes perfect sense.
In HDR1 you collect all filenames that start with 'Spatial/csp'; then
contain zero or more wildcard characters; then the last character before
the dot should *not* be
Hi all!
Maybe I just didn't find the answer. Sorry in that case...
I am wondering how to manage different targets.
What I would like to handle are targets like
release
debug
demo release (additionals defines)
first customer oem release (other additional defines)
second customer oem release (again
30 matches
Mail list logo
