Quick question about the cmake xcode project generator. I can run cmake and
build my project just fine using cmake under Leopard from the terminal and
from xcode, so there is no build problem. I was wondering if anyone has
code completion working for their project? To be more specific, when usin
Looks like QTDIR is checked last, so it will always use the one found in my
path. I was (incorrectly) expecting QTDIR to be an override, but it
functions more like a safety net.
-thanks
On Wed, Mar 11, 2009 at 1:34 PM, Doug Henry
> wrote:
> thanks for the responses. I may have mi
qmake
/tools/lin64/bin/qmake
(lin64):~/tmp/build$ ls /home/dhenry/qtsdk-2009.01/qt/bin/qmake
/home/dhenry/qtsdk-2009.01/qt/bin/qmake
On Wed, Mar 11, 2009 at 12:58 PM, Pau Garcia i Quiles
wrote:
> On Wed, Mar 11, 2009 at 5:48 PM, Boudewijn Rempt wrote:
> > On Wed, 11 Mar 2009, Doug He
I have multiple Qt installations and would like to know how I guide the
find_package(Qt4) command to find the correct one. I assume there is a
variable I can set which defines the search path, which will allow me to
change the path to find a different installed version. Thanks.
:doug
___
I'm trying to follow this thread because it seems like it might be important to me, but I'm not sure I understand the root problem. The problem isn't finding zlib? The problem isn't using custom modules? I guess there is something special about the custom zlib module that cmake's module doesn't
I have not seen a repo for cmake files like that, but I have a feeling there are cmake build files for zlib, png, etc in the VTK source (vtk.org).On 10/25/06,
Luigi Calori <[EMAIL PROTECTED]> wrote:
Kedzierski, Artur CIV NAVSURFWARCENDIV CORONA wrote:> Hi,>> On Windows side, I built a
Done. Bug #3980.On 10/25/06, Brad King <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> Looks like I may have missed a couple options (-R and -KPIC). As far as> I can tell, the compiler should work exactly like the already supported> SunOS version of the compiler. Just copy the o
Since no one has used thiscompiler before I don't mind including the option until someone
complains their version doesn't have it.I would think the same options would apply to SunOS.cmake.
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailm
The sun compilers also have aliases: suncc, sunCC, sunf95, etc. Maybe those names should be used instead? I assume this is as easy as making a Linux-sunCC.cmake file.On 10/25/06,
Brad King <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> Before I commit anything, I would like to verify
could have f77 from either set of compilers but each requires different compiler options. Can this be done using cmake?
On 10/25/06, Brad King <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> I noticed that the default options for build mode may be a bit strange> for sun compilers. The
I noticed that the default options for build mode may be a bit strange for sun compilers. The release mode uses -xO2 and the minimum size mode uses -xO3 (higher optimization level?). There seems to be an option -xspace which reads:
-xspace Do not do optimizations that increase code
Looks like I may have missed a couple options (-R and -KPIC). As far as I can tell, the compiler should work exactly like the already supported SunOS version of the compiler. Just copy the options from the already included
SunOS.cmake file, which are almost the same as the file I sent you.On 10/
hack" strategy sometimes works.
On 10/23/06, Brad King <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> I am trying to use the sun studio compiler under linux and I am having a> terrible time getting past the cmake compiler tests. I'm not sure what> the error messages are tell
I am trying to use the sun studio compiler under linux and I am having a terrible time getting past the cmake compiler tests. I'm not sure what the error messages are telling me, but it looks like some incorrect flags are being passed in. I extracted the short test program from
CMakeTestCXXCompi
Thanks for the explaination. I added the files to the target list as suggested by Filipe, and it worked. It is nice to know this is the proper way to do it.On 8/28/06,
Brad King <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> No, since it is a dependency of a source file that is includ
cmake will not run the custom command anymore. I suspect that the source files I generate this way are created because they are in the list as you suggest.
On 8/28/06, Filipe Sousa <[EMAIL PROTECTED]> wrote:
Doug Henry wrote:> Something about the custom command behavior has changed sli
Something about the custom command behavior has changed slightly and I am hoping I am just missing something. I have been able to do the following in the past:## reswrap log.sql file#SET(DBNAME log_sql)
SET(DBS ${PROJECT_BINARY_DIR}/${DBNAME}.h)SET(LOGSQL ${PROJECT_SOURCE_DIR}/../data/log.sql)ADD_
I assume this is a special case and cmake is capable of building fortran projects?On 5/30/06, Brad King <
[EMAIL PROTECTED]> wrote:Doug Henry wrote:> Has there been any resolution to this issue? I receive a variety of
> mod.proxy errors when compiling fortran using cmake 2.4.2.No one has had time
Has there been any resolution to this issue? I receive a variety of mod.proxy errors when compiling fortran using cmake 2.4.2.On 11/10/05, Paulo Jabardo
<[EMAIL PROTECTED]> wrote:
Sorry, I musta have mada some very silliy mistake when originally posting: My CMakeLists.txt is as follows: In the t
I have g77 and ifort fortran compilers installed under linux. For a few projects I would like to force the use of ifort if available. Is there a way to "suggest" the order the cmake automatic detection looks for fortran compilers?
___
CMake mailing lis
PROTECTED]> wrote:
Doug Henry wrote:> actually, I have found if I change the following entry (add expat to the> linker flags) in cmxmlrpc/CMakeLists.txt this problem goes away:>> TARGET_LINK_LIBRARIES(xrtest cmXMLRPC cmexpat expat ${CMAKE_DL_LIBS})
From where is that other "e
actually, I have found if I change the following entry (add expat to the linker flags) in cmxmlrpc/CMakeLists.txt this problem goes away:TARGET_LINK_LIBRARIES(xrtest cmXMLRPC cmexpat expat ${CMAKE_DL_LIBS})
On 5/26/06, Doug Henry <[EMAIL PROTECTED]> wrote:
I receive the errors below when bu
I receive the errors below when building versions 2.2.3 and 2.4.2. It looks like the cmexpat library is not linking in when cmXMLRPC library is used. I have ./Utilities/cmexpat/libcmexpat.a so it did build, not sure what would cause this.
[TOOLS cmake-2.4.2]$ makeLinking C executable ../../bin/xr
23 matches
Mail list logo
