Maik Beckmann schrieb:
If I do a
find_library ( SOMEVAR ws2_32 )
then cmake finds the wrong one at "C:/WINDOWS/system32/ws2_32.dll"
(which makes no sense and fails later) until I set the LIB environment
variable to the mingw dirs. And setting INCLUDE might be as good.
Sorry, you lost me
Server Levent Yilmaz wrote:
However the executables are invalid. The reason, which took me a while
to figure out, is the use of shared libraries, which as I mentioned, is
not allowed in the Catamount system. The front-end wrappers
unfortunately do not automatically detect a possible misuse and
Am Samstag 17 Mai 2008 23:22:02 schrieb Hendrik Sattler:
> Maik Beckmann schrieb:
> > However, this
> > SET PATH=.;C:\mingw\bin;C:\cmake\bin
> > looks strange, please try
> > SET PATH=%PATH%;C:\mingw\bin;C:\cmake\bin
> >
> > I use the combination WinXP + cmake-2.6.0 + mingw at least twice a wee
Maik Beckmann schrieb:
However, this
SET PATH=.;C:\mingw\bin;C:\cmake\bin
looks strange, please try
SET PATH=%PATH%;C:\mingw\bin;C:\cmake\bin
I use the combination WinXP + cmake-2.6.0 + mingw at least twice a week,
without problems.
If I do a
find_library ( SOMEVAR ws2_32 )
then cmak
On Fri, May 16, 2008 at 5:59 PM, Brad King <[EMAIL PROTECTED]> wrote:
>
> CMake has not been taught about this compiler before. I've just
> committed some changes to support the Portland Group Fortran compiler in
> CMake CVS.
Thanks Brad, with the HEAD version the project configures and builds
Hello
Another patch :)
(against CMake-2.6.0)
Issues:
- SET(ENV{LC_ALL} C) does not work under Windows: it should be done
each time the macro Subversion_WC_INFO is run.
- svn log -r takes too long
So I've splitted macro Subversion_WC_INFO and created a new one:
Subversion_WC_LOG
--
Tanguy Krot
Philip,
Thanks! I actaully was trying that way. But, changed it. Stupid me.
I copied the linked script as-is and it worked. It found the lib64 path,
with no problem.
The problem I was having before (that made me try the PKG_CONFIG) was caused
by not having the ENABLE_TESTING() macro in the t
Hello
I've noticed some lake of features inside FindQt4.cmake qt4_automoc macro
This patch intend to fix this.
(patch against CMake 2.6.0)
How current qt4_automoc works:
Looks for files that contain string: #include "*.moc"
Issues:
- With QMake, it is possible to specify also #include "moc_*.c
On 17.05.08 18:06:11, Dmitry Marakasov wrote:
> --- CMakeLists.txt begins here ---
> # project name
> PROJECT(Memonix)
>
> # depends
> set(SDL_CONFIG "sdl-config" CACHE STRING "Path to sdl-config script")
Thats broken by design, what if sdl-config is not in my PATH?
> FIND_PACKAGE(SDL REQUIRED)
Am Samstag 17 Mai 2008 18:11:02 schrieb Phil Pellouchoud:
> I saw somewhere online talk about "process_begin" and being a path issue
> (i.e. finding the wrong tools, etc...) for a different problem. So I
> had adjusted my path (SET PATH=.;C:\mingw\bin;C:\cmake\bin). But still
> no luck...
>
> -ph
I saw somewhere online talk about "process_begin" and being a path issue
(i.e. finding the wrong tools, etc...) for a different problem. So I
had adjusted my path (SET PATH=.;C:\mingw\bin;C:\cmake\bin). But still
no luck...
-phil
CMakeError.log
Determining if the C compiler works fail
Phil Pellouchoud schrieb:
I did try to compile a simple hello world program, and I can do it on
the command line:
gcc -o test test.cpp
Builds and runs fine.
I am using Windows XP SP2
GCC version is this:
S:\software\packages\utility\build>gcc -v
Using built-in specs.
Target: i386-pc-mingw32
Co
I did try to compile a simple hello world program, and I can do it on
the command line:
gcc -o test test.cpp
Builds and runs fine.
I am using Windows XP SP2
GCC version is this:
S:\software\packages\utility\build>gcc -v
Using built-in specs.
Target: i386-pc-mingw32
Configured with: ../gcc-4.3.0/
On Fri, May 16, 2008 at 9:56 PM, Edson Tadeu <[EMAIL PROTECTED]> wrote:
> (Not even mentioning the indent style). It seems that there is a
> transition going on from uppercase to lowercase in the recent CMakeLists...
> I don't know what style to settle for my new CMakeLists.txt's, because if I
>
Phil Pellouchoud schrieb:
I have been trying to get cmake to work with MinGW.
I have trolled around the net and looked for clues and tried a bunch of
things without success. Here are the particulars:
Any ideas?
Did you try to compile a simple hello world from command line? Does it
I have been trying to get cmake to work with MinGW.
I have trolled around the net and looked for clues and tried a bunch of
things without success. Here are the particulars:
- cmake 2.6
- cmake installed C:\cmake
- mingw installed C:\mingw
- SET PATH=.;C:\mingw\bin;C:\cmake\bin
Here's
On Sat, May 17, 2008 at 10:28 AM, Michael Bowerman <
[EMAIL PROTECTED]> wrote:
> List,
>
> I am trying to use cppunit for my automated tests. I have the project
> compiling with autotools. But, I am moving to cmake to build on windows
> (while the project is still small-ish).
>
> So, is the prop
List,
I am trying to use cppunit for my automated tests. I have the project
compiling with autotools. But, I am moving to cmake to build on windows
(while the project is still small-ish).
So, is the proper way to look for CppUnit to use pkg_check_modules?
cppunit exists in /usr/include/cppunit
Hi!
I've got some breakages after switch to CMake 2.6.0, and I'm not
sure how to fix those in a correct way. The app in question is
memonix:
http://www.viewizard.com/download/MemonixSourceCode_1.6_070713.zip
(I'm not related to authors of this software, but CMakeLists.txt
there is by me).
Here'
19 matches
Mail list logo