On Friday 01 August 2008 20:06:15 Hari Sundar wrote:
Hi,
I have Cmake set up to generate project files for VC6. This works
fine. The project can only be compiled with the VC6 compiler because
of legacy code.
What I am interested in is to know if it is possible to generate a VC
7,8,9
Special thanks at all. It works fine without any error or warning.
so long
jd
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Bill,
I can reproduce my infinite dependencie problem. Every time I type
'make' it redoes the swig step, using cmake 2.4.5 I cannot reproduce
the issue.
How do I track this thing down ? Otherwise steps are simply:
svn co https://gdcm.svn.sourceforge.net/svnroot/gdcm/trunk
mkdir bla
cd bla
I can try a couple of the questions:
For ctest you should have something like the following in your
CMakeLists.txt file (or a file included by CMakeLists.txt:
# Add a variable that the user can set to enable/disable testing
OPTION(BUILD_TESTING Build CTest Testing ON)
IF(BUILD_TESTING)
What happens when you type make install ? Are there install*
commands in the CMakeLists.txt files?
--
Mike Jackson Senior Research Engineer
Innovative Management Technology Services
On Aug 3, 2008, at 10:36 PM, Michael Masters wrote:
I'm trying to figure out the current cmake build in
On Aug 1, 2008, at 11:27 AM, Jan Dinger wrote:
Hello folks,
I'll use cmake for my qt-apps, but I've a little trouble. If I run
cmake under Debian-sid all works fine, next tray I run cmake under
Debian-lenny, and now I'vr trouble. Cmake failed with an error:
###snip###
Please set the
Andrew Sayman wrote:
There were other potential ways to resolve the dependencies other than
such a massive static library, but I don't know of a good CMake-style
way to integrate the --start-group and --end-group flags without
resorting to a bunch of really terse coding in my CMakeLists.txt.
On Mon, Aug 4, 2008 at 4:16 PM, Brad King [EMAIL PROTECTED] wrote:
It definitely fixed the problem. Thanks a bunch.
Okay, I'll look at using these everywhere possible by default.
Does this means 'make VERBOSE=1' will not be verbose anymore ?
--
Mathieu
Hello guys,
I have one project is compiling and linking propertly.
When I tried to include this project in a bigger project, it's not
correctly linking.
I generated both using CMAKE_VERBOSE_MAKEFILE:bool=true and I
eliminated all differences in the compile and link
Mathieu Malaterre wrote:
Bill,
I can reproduce my infinite dependencie problem. Every time I type
'make' it redoes the swig step, using cmake 2.4.5 I cannot reproduce
the issue.
How do I track this thing down ? Otherwise steps are simply:
svn co
On Aug 4, 2008, at 8:34 AM, Vitor Vasconcelos Araujo Silva wrote:
Hello guys,
I have one project is compiling and linking propertly.
When I tried to include this project in a bigger project, it's not
correctly linking.
I generated both using
On Mon, Aug 4, 2008 at 4:46 PM, Bill Hoffman [EMAIL PROTECTED] wrote:
Mathieu Malaterre wrote:
Bill,
I can reproduce my infinite dependencie problem. Every time I type
'make' it redoes the swig step, using cmake 2.4.5 I cannot reproduce
the issue.
How do I track this thing down ?
Did you build both static and shared Qt and install it in the same place?
That would produce a bad install of Qt. That might explain why you
have both libQtXml.a and libQtXml4.a
Clint
Yes, I have both versions, but in different directories.
I'll try clean the directory and
Hello again,
I'm still trying to make CMake compile my Symbian project using a gcc (GCCE)
toolchain and I have some progress to report since my last posting (see
http://www.cmake.org/pipermail/cmake/2008-July/022868.html
BLOCKED::http://www.cmake.org/pipermail/cmake/2008-July/022868.html ) as
Brad King wrote:
Andrew Sayman wrote:
It definitely fixed the problem. Thanks a bunch.
Okay, I'll look at using these everywhere possible by default.
Done:
/cvsroot/CMake/CMake/Modules/CMakeCInformation.cmake,v --
Modules/CMakeCInformation.cmake
new revision: 1.22; previous revision: 1.21
Mathieu Malaterre wrote:
As a side note, linux user are second class citizen and AFAIK do not
get automated RC build, right ? win user are simply a click away of
trying RC.
No, I do a full build for each RC, all platforms that are done for the
release are done for the RC's.
And AMD64 people
[EMAIL PROTECTED] wrote:
Hello again,
I'm still trying to make CMake compile my Symbian project using a gcc
(GCCE) toolchain and I have some progress to report since my last
posting (see http://www.cmake.org/pipermail/cmake/2008-July/022868.html
Mathieu Malaterre wrote:
On Mon, Aug 4, 2008 at 4:16 PM, Brad King [EMAIL PROTECTED] wrote:
It definitely fixed the problem. Thanks a bunch.
Okay, I'll look at using these everywhere possible by default.
Does this means 'make VERBOSE=1' will not be verbose anymore ?
No, the archiving rules
On Mon, Aug 4, 2008 at 5:37 PM, Bill Hoffman [EMAIL PROTECTED] wrote:
Mathieu Malaterre wrote:
As a side note, linux user are second class citizen and AFAIK do not
get automated RC build, right ? win user are simply a click away of
trying RC.
No, I do a full build for each RC, all platforms
Am Montag, 4. August 2008 17:48:28 schrieb Mathieu Malaterre:
That was not really my main concern anyway, instead I am more
concerned with the patch done for debian people (admittedly I dont
understand what they are trying to do):
Hendrik Sattler wrote:
Am Montag, 4. August 2008 17:48:28 schrieb Mathieu Malaterre:
That was not really my main concern anyway, instead I am more
concerned with the patch done for debian people (admittedly I dont
understand what they are trying to do):
Mathieu Malaterre wrote:
I can reproduce my infinite dependencie problem. Every time I type
'make' it redoes the swig step, using cmake 2.4.5 I cannot reproduce
the issue.
How do I track this thing down ? Otherwise steps are simply:
svn co
Am Montag, 4. August 2008 18:02:15 schrieb Bill Hoffman:
Hendrik Sattler wrote:
Am Montag, 4. August 2008 17:48:28 schrieb Mathieu Malaterre:
That was not really my main concern anyway, instead I am more
concerned with the patch done for debian people (admittedly I dont
understand what
On Mon, Aug 4, 2008 at 7:04 PM, Brad King [EMAIL PROTECTED] wrote:
Mathieu Malaterre wrote:
I can reproduce my infinite dependencie problem. Every time I type
'make' it redoes the swig step, using cmake 2.4.5 I cannot reproduce
the issue.
How do I track this thing down ? Otherwise steps
Mathieu Malaterre wrote:
In order to support -interface, one would need to fix the MACRO in
UseSWIG.cmake:
MACRO(SWIG_GET_EXTRA_OUTPUT_FILES language outfiles generatedpath infile)
GET_SOURCE_FILE_PROPERTY(SWIG_GET_EXTRA_OUTPUT_FILES_module_basename
${infile} SWIG_MODULE_NAME)
On Sunday 03 August 2008, [EMAIL PROTECTED] wrote:
hi, there
I am trying to compile a kde4 development tutorial c++ program with
cmake but got the
that's the tutorial in the cmake wiki, right ?
This is unfortunately out of date, I'll fix it next week at akademy.
kde4_automoc() doesn't exist
CHECK_TYPE_SIZE returns incorrect (empty) values of types sizes when
the LDFLAGS variable contains -Wl,--gc-sections.
This bug causes compilation failures in probably all packages which
use CHECK_TYPE_SIZE.
I'm attaching 2 files which help to reproduce this bug.
Steps to reproduce:
1. Save the
Hi all,
I tried to use cmake 2.7 to compile a gnome application under Fedora 9,
and I got a failure.
It seems that FindGTK.cmake from the modules directory is severe
outdated, looking for gtk 1.2, in a format used a few years ago. Can
somebody please update this script to be more recent?
I
Hi,
just a note: please keep the mails on the list, so it can help everybody.
On Friday 01 August 2008, 王汉斌 wrote:
Hi Alex,
Thanks for the replying. My aim is to set up a cross-compling toolchain,
just like a makefile, to tell the platform environment how to bulid the
project.
Ok so far.
On Mon, Aug 4, 2008 at 10:16 AM, Brad King [EMAIL PROTECTED] wrote:
It doesn't have any notion of one archive
depending non-circularly on others?
Nope. This project is full of circular dependencies and incorrectly
mixing C and C++ code at certain points. I've managed to find an
ordering that
On Friday 01 August 2008, Phil Smith wrote:
Sure, here are two files:
ctsc.fascii -- CheckTypeSizeC.c compiled with the Dignus -fascii option
ctsc.nofascii -- CheckTypeSizeC.c compiled without the Dignus -fascii
option
The file indeed looks different than all object files I have ever seen.
On Friday 01 August 2008, Phil Smith wrote:
Did you set the CMAKE_EXECUTABLE_SUFFIX appropriately for z/OS ?
If by 'executable' you mean 'linked object', i.e., a .EXE if this was
Windows, then I *think* I have: in zosport.cmake is:
SET(CMAKE_LINKER linkit.bat)
On Monday 04 August 2008, Georgios Petasis wrote:
Hi all,
I tried to use cmake 2.7 to compile a gnome application under Fedora 9,
and I got a failure.
It seems that FindGTK.cmake from the modules directory is severe
outdated, looking for gtk 1.2, in a format used a few years ago. Can
Arfrever Frehtes Taifersar Arahesis wrote:
CHECK_TYPE_SIZE returns incorrect (empty) values of types sizes when
the LDFLAGS variable contains -Wl,--gc-sections.
This bug causes compilation failures in probably all packages which
use CHECK_TYPE_SIZE.
I'm attaching 2 files which help to
On Monday 04 August 2008, Georgios Petasis wrote:
Hi all,
Recent versions of Tcl/Tk have added a new stubs library for the themed
widget set.
I have updated FindTclStub.cmake to also locate this library.
George
Please create an entry in the cmake bug tracker for this and attach the file
On Friday 01 August 2008, Andreas Pokorny wrote:
Hello,
We are building for Win32, WinCE, QNX, Linux and hopefully soon also
Symbian, with mostly
cross compile setups using cmake. But note, that right now cross
compiling only works for gnu make and nmake.
You wanted to clean up the WinCE
I'm not sure, but when I look at the -fascii-ized version of CheckTypeSizeC.o
using my text editor on Windows, I find:
INFO:sizeof[8]
as I'd expect.
Well, actually I know one answer: the square brackets are a problematic
character, and depend on the codepage. I haven't really looked
Hi, all
Just for other cmake newbies, like me, who run into cross-compiler that
is not able to build a simple program by default without special flags.
When I go on reading the wiki
http://www.cmake.org/Wiki/CMake_Cross_Compiling
I found that I should use CMakeForceCompiler module to bypass build
Hi,
Would it be readily implemented so that the error message can be copied to
clipboard from the Error panel?
Would anybody else find this useful?
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
39 matches
Mail list logo
