I'm writing a better Find module for using some libraries compiled
with MSYS under MSVC (FFMPEG to be more precise).
My problem is that FIND_LIBRARY() seems to only search for .lib files,
while MSYS static library files are named .a (even though they *are*
.lib files compatible with MSVC).
S
On 6/15/07, Jon W <[EMAIL PROTECTED]> wrote:
>
> Was the COMPILE_LANGUAGE property ever incorporated into cmake?
> http://www.mail-archive.com/cmake@cmake.org/msg01326.html
It got called the LANGUAGE property, as per Bill's e-mail 5 days ago.
[EMAIL PROTECTED] ~/My Builds/CMake/Tests
$ less
Hi,
Thanks for that link to the latest version. It didn't help me unfortunately, Im
getting
the same error. Other suggestion are welcome.
I just tried Express Visual Studio 2008, and didn't work either. Here is the
error
message:
---
Bill's release candidate email to the list earlier this month (including the
download link and change descriptions) is in the list archives:
http://www.cmake.org/pipermail/cmake/2007-June/014461.html
On 6/15/07, Lars Nygard <[EMAIL PROTECTED]> wrote:
Hi David,
Thaks for your email. I tried w
Here is the download link:
http://www.cmake.org/files/v2.4/
On 6/15/07, Lars Nygard <[EMAIL PROTECTED]> wrote:
Hi David,
Thaks for your email. I tried what you said but I still get the same
error.
Where can I download cmake 2.4.7? The latest version on the site is
2.4.6...
greets,
Lars Nygard
On Friday 15 June 2007 13:22, Lars Nygard wrote:
> Hi,
>
> Im using Visual Studio .NET 2003, Window XP service pack2 (with all latest
> updates) and Cmake 2.4 patch 6
> This is part of the error file from cmake.
> ***
>*** Dete
Hi David,
Thaks for your email. I tried what you said but I still get the same error.
Where can I download cmake 2.4.7? The latest version on the site is
2.4.6...
greets,
Lars Nygard
- Original Message
From: David Cole <[EMAIL PROTECTED]>
To: Lars Nygard <[EMAIL PROTECTED]>
Cc: cmake@cm
This file name: ...
c:\Documents and Settings\lars\Desktop\Insight
Toolkit\myPrograms\ImageRegist
rationBin\CMakeFiles\CMakeTmp\CMakeFiles\CMakeTmp\CMakeFiles\CMakeTmp\CMakeFiles\CMakeTmp\CMakeFiles\CMakeTmp\CMakeFiles\CMakeTmp\CMakeFiles\CMakeTmp\cmTryCompileExec.dir\Debug
...is 254 characters lo
Hi,
Im having some problems with cmake and Visual studio 2003 .NET. It has worked
good some time, but a few weeks I suddenly got "unable to compile a simple test
program".
When I re-install visual studio, it sometimes works for a while but after a few
configuration
i get this error. I can't unde
On Friday 15 June 2007 12:28, Peter Visser wrote:
> > > INSTALL(TARGETS helloworld
> > > RUNTIME DESTINATION bin STRIP_ALWAYS
> > > LIBRARY DESTINATION lib STRIP_NEVER
> > > ARCHIVE DESTINATION lib STRIP_NEVER
> > >)
> > >
> > >
On 6/15/07, Jon W <[EMAIL PROTECTED]> wrote:
I'm using cmake to generate solutions for Visual Studio 2003. With
several of the projects I need to compile the *.c files as c++ code.
I'm trying to get the /TP flag to override the /TC flag that is
automatically generated by cmake, but not having m
On 6/15/07, Jon W <[EMAIL PROTECTED]> wrote:
I'm using cmake to generate solutions for Visual Studio 2003. With
several of the projects I need to compile the *.c files as c++ code.
I'm trying to get the /TP flag to override the /TC flag that is
automatically generated by cmake, but not having m
I'm using cmake to generate solutions for Visual Studio 2003. With
several of the projects I need to compile the *.c files as c++ code.
I'm trying to get the /TP flag to override the /TC flag that is
automatically generated by cmake, but not having much luck. I've read
the mailing archive, and
> INSTALL(TARGETS helloworld
> RUNTIME DESTINATION bin STRIP_ALWAYS
> LIBRARY DESTINATION lib STRIP_NEVER
> ARCHIVE DESTINATION lib STRIP_NEVER
>)
>
> In my case that would work very well.
I guess you would do it this way for
On Friday 15 June 2007 11:47, Peter Visser wrote:
> > We'll do something about it.
> > How about adding options to the install() command like STRIP_ALWAYS and
> > STRIP_NEVER ?
>
> Do you mean something like this:
>
> INSTALL(TARGETS helloworld
> RUNTIME DESTINATION bin STRIP_ALWA
We'll do something about it.
How about adding options to the install() command like STRIP_ALWAYS and
STRIP_NEVER ?
Do you mean something like this:
INSTALL(TARGETS helloworld
RUNTIME DESTINATION bin STRIP_ALWAYS
LIBRARY DESTINATION lib STRIP_NEVER
On Friday 15 June 2007 03:04, Peter Visser wrote:
> Hello Alex,
>
> Hereby a minimal testcase, I used the CMakeExample and added some
> INSTALL/PACK rules.
Thanks.
> On 6/14/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
> > On Thursday 14 June 2007 16:36, Peter Visser wrote:
> > > I rather li
Brandon Van Every wrote:
On 6/15/07, vincent ROULLIER <[EMAIL PROTECTED]> wrote:
Hi,
I would like to compile ITK on OS X for windows. I'm using cmake with
mingw to
compile ITK. But I have some problem to configure CMAKE parameters to
compile itk.
Is there any CMAKE parameters like prefix or
On 6/15/07, vincent ROULLIER <[EMAIL PROTECTED]> wrote:
Hi,
I would like to compile ITK on OS X for windows. I'm using cmake with mingw to
compile ITK. But I have some problem to configure CMAKE parameters to compile
itk.
Is there any CMAKE parameters like prefix or target in configure ??
Can
ok, thanks
Regards,
Jens-Michael
|->
|"Mathieu Malaterre" |
|<[EMAIL PROTECTED]|
|com> |
| |
|14.06.2007 10:20 |
|---
Hi,
In my CMake installation on Windows, there are two directory with
seemingly identical contents:
c:/Program Files/CMake 2.4/share/CMake
c:/Program Files/CMake 2.4/share/cmake-2.4
Could someone care to explain the difference?
--
/Jesper
___
CMake m
Hi,
I would like to compile ITK on OS X for windows. I'm using cmake with mingw to
compile ITK. But I have some problem to configure CMAKE parameters to compile itk.
Is there any CMAKE parameters like prefix or target in configure ??
Can somebody help me ?
Vincent
_
On Friday 15 June 2007 08:37, Jesper Eskilson wrote:
> Hi,
>
> In my CMake installation on Windows, there are two directory with
> seemingly identical contents:
>
> c:/Program Files/CMake 2.4/share/CMake
The name of the subdir was changed from CMake/ to cmake-2.4/, so maybe this is
still there fr
Hi,
On Friday 15 June 2007 02:54, kitts wrote:
...
> I cannot publish the source but let me describe how i do it now with my
> project at work.
>
> In the top level cmakelists.txt I include the subdirectories of the various
> modules in our project. The first subdirectory included is called platfo
2007/6/15, kitts <[EMAIL PROTECTED]>:
On Thursday 14 Jun 2007 12:23:07 pm Jesper Eskilson wrote:
> Is it really impossible to pass an option to the linker when creating a
> static library?
I have not gone through the whole thread but i think the function
SET_TARGET_PROPERTIES(TARGET LINK_FLAGS
On Thursday 14 Jun 2007 12:23:07 pm Jesper Eskilson wrote:
> Is it really impossible to pass an option to the linker when creating a
> static library?
I have not gone through the whole thread but i think the function
SET_TARGET_PROPERTIES(TARGET LINK_FLAGS "XYZ") can do it.
The problem i foresee
On Thursday 14 Jun 2007 6:25:24 pm Brandon Van Every wrote:
> On 6/14/07, Alexander Neundorf <[EMAIL PROTECTED]> wrote:
> > Have a look at this page, it documents current CMake cvs HEAD:
> > http://www.cmake.org/Wiki/CMake_Cross_Compiling
> >
> > I'm happy about questions, comments, ideas etc.
>
>
Hi there,
I have a problem with installing libs and executables. I experienced this
problem on CMake 2.4.6 (32-Bit Windows, Visual Studio 8):
I can create my .sln-File without problems and do all the building and
running INSTALL as expected. Having a look in my install_manifest.txt ist
says some
On 6/15/07, Philippe Fremy <[EMAIL PROTECTED]> wrote:
Filip Brcic wrote:
> Дана четвртак 14 јун 2007, Philippe Fremy је написао(ла):
>> Hi,
>>
>> In my project, I have very often a pattern like this:
>> a.cpp:
>> #include "z.h"
>>
>> b.cpp:
>> #include "z.h"
>>
>> c.cpp:
>> #include "z.h"
>>
Filip Brcic wrote:
> Дана четвртак 14 јун 2007, Philippe Fremy је написао(ла):
>> Hi,
>>
>> In my project, I have very often a pattern like this:
>> a.cpp:
>> #include "z.h"
>>
>> b.cpp:
>> #include "z.h"
>>
>> c.cpp:
>> #include "z.h"
>>
>>
>> z.cpp:
>> #include "z.h"
>>
>>
>> If I change z.h
Hello Alex,
Hereby a minimal testcase, I used the CMakeExample and added some
INSTALL/PACK rules.
Cheers,
Peter.
WinXP/MinGW build output:
$ cmake -G "MSYS Makefiles" ../.
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: C:/Pro
31 matches
Mail list logo
