Project files are not listed in "File Groups" section of KDevelop
(3.5.2) when project file is generated through "cmake -GKDevelop3"
I generate kdevelop project files via cmake 2.6.1 kdevelop3 generator.
When I open the project, no file of my project is shown in "File
Groups" section or "Classes" s
2008-08-06 02:56:52 Bill Hoffman napisał(a):
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 2008-08-05 00:01:51 Bill Hoffman napisał(a):
> >> Arfrever Frehtes Taifersar Arahesis wrote:
> >>> CHECK_TYPE_SIZE returns incorrect (empty) values of types sizes when
> >>> the LDFLAGS variable contains "
Hi, Alex
2008/8/6 Alexander Neundorf <[EMAIL PROTECTED]>:
> On Tuesday 05 August 2008, ning wrote:
>> 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
>>
Arfrever Frehtes Taifersar Arahesis wrote:
2008-08-05 00:01:51 Bill Hoffman napisał(a):
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 pro
2008-08-05 00:01:51 Bill Hoffman napisał(a):
> 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
> > u
On Tuesday 05 August 2008, Phil Smith wrote:
> Re the link command, thanks:
> SET(CMAKE_C_LINK_EXECUTABLE "c:/progra~1/dignus/linkit.bat -o
> ./ ") seems to be working much better!
>
> As for the ForceCompiler stuff, I think I understand what you're getting
> at, but am reluctant to be qu
On Tuesday 05 August 2008, Phil Smith wrote:
> Nope, that didn't do it. I tried it with and without double quotes around
> the value: no -fascii was passed in either case.
>From a clean build tree, right ?
It should work.
If it doesn't, search for CMAKE_C_COMPILER_ARG1 and check using
MESSAGE(
Re the link command, thanks:
SET(CMAKE_C_LINK_EXECUTABLE "c:/progra~1/dignus/linkit.bat -o
./ ")
seems to be working much better!
As for the ForceCompiler stuff, I think I understand what you're getting at,
but am reluctant to be quite that pure since it's likely to require a bunch
mo
Nope, that didn't do it. I tried it with and without double quotes around the
value: no -fascii was passed in either case. However, I'm tentatively
declaring victory (very tentatively -- I've had it working before, but for the
wrong reasons, such as NOT doing a linkedit and having it happen to
On Tuesday 05 August 2008, ning wrote:
> 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 s
Hi,
On Tuesday 05 August 2008, Phil Smith wrote:
> Next issue: linking. I have a toolchain file now that looks like this:
>
>
> # Tell CMAKE the target system name
> SET(CMAKE_SYSTEM_NAME "ZOS")
>
> # Specify the cross-compilers
> SET(CM
On Tuesday 05 August 2008, Phil Smith wrote:
> 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
Next issue: linking. I have a toolchain file now that looks like this:
# Tell CMAKE the target system name
SET(CMAKE_SYSTEM_NAME "ZOS")
# Specify the cross-compilers
SET(CMAKE_C_COMPILER "c:/progra~1/dignus/cc.bat")
SET(CMAKE_CXX_COMP
No you didn't; i forgot to mention version number. I just moved up to 2.6
patch 1 but didn't think about trying Ctrl-C. Thanks.
Trying to get CMake to take over some projects on Vista 64 bit where the
Windows SDK cl.exe is the compiler. If I select "NMake Makefiles" generator
CMake never comes
On Tuesday 05 August 2008 19:10:04 Mehdi Rabah wrote:
> Hi,
>
> I was wondering what is the default working directory while debugging a
> target in visual studio ? Is it $EXECUTABLE_OUTPUT_PATH ?
As I know, CMake doesn't deal with debugging settings in VS projects, because
they are stored in propr
Hi,
I was wondering what is the default working directory while debugging a
target in visual studio ? Is it $EXECUTABLE_OUTPUT_PATH ?
I'm using a relative path for finding a file in my code and I have a problem
because the working dir should be (for me) $EXECUTABLE_OUTPUT_PATH/Debug or
$EXECUTABL
Iker Arizmendi wrote:
> I've run into some trouble with how CMake 2.4.2 (and perhaps
> later) handles the string "$ORIGIN" when it appears as part of
> an RPATH. I've gotten around the trouble (see below), but would
> appreciate any pointers on the correct way to use "$ORIGIN".
This will work with
Ah. I was showing my ignorance; I've only used 2.6, and thought that was the
window he meant!
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Jackson
Sent: Tuesday, August 05, 2008 9:16 AM
To: Roger Martin
Cc: cmake@cmake.org
Subject: Re: [CMake] Error panels allow copy of mes
are you using CMake version 2.4 on windows? Try Version 2.6.x on
Windows as it comes with a new GUI app called cmake-gui. This
application has a "log" window where the output from the cmake
command is easily copied from.
--
Mike Jackson Senior Research Engineer
Innovative Management & Tec
I believe that works -- C gets the text. (Some Windows apps do this,
some don't - wish the all did!)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Martin
Sent: Tuesday, August 05, 2008 12:29 AM
To: cmake@cmake.org
Subject: [CMake] Error panels allow copy of message?
Hi,
W
Hello Clinton,
I cleaned and rebuild my Qt version and now everything works fine. As
you said, I had a mix of static and dynamic libraries in the same directory.
Thanks.
Did you build both static and shared Qt and install it in the same place?
That would produce a bad instal
21 matches
Mail list logo
