Re: [CMake] Project files are not listed when project file is generated through "cmake -GKDevelop3"

2008/8/7 Alexander Neundorf <[EMAIL PROTECTED]>: > On Wednesday 06 August 2008, Andreas Pakulat wrote: >> On 06.08.08 20:29:07, Yogesh Marwaha wrote: >> > 2008/8/6 Andreas Pakulat <[EMAIL PROTECTED]>: >> > > It would be interesting to s

Re: [CMake] Project files are not listed when project file is generated through "cmake -GKDevelop3"

2008/8/6 Andreas Pakulat <[EMAIL PROTECTED]>: > It would be interesting to see how the file initially looked. KDevelop > automatically removes any entries which point to non-existing files and > I guess the cmake generator has wrong assumptions about what it can put > into the filelist. > Here is t

[CMake] Project files are not listed when project file is generated through "cmake -GKDevelop3"

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

Re: [CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

...and it turns out that I needed something like KDE_EXPORT for exporting(?) the symbols in the shared library. So the whole problem was caused by ...still not sure... but certainly looks not to be caused by cmake. It just occured to me, concentrating on the 't" stuff, that I should see the result

Re: [CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

2008/7/14 Bill Hoffman <[EMAIL PROTECTED]>: > OK, so this looks like some sort of moc issue. Are you running moc on the > header? You might want to run nm on all the .o files and find out where the > little "t" stuff is located. Could it be that you have more than one file > called the same thin

Re: [CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

2008/7/13 Bill Hoffman <[EMAIL PROTECTED]>: > Little t usually means local linkage, so that would be why you can not see > the symbols from an external library. I don't think this is a CMake issue, > but rather a C++ issue of some sort. What does the header file for > GApplication and the .cxx fi

Re: [CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

First of all, *sorry* for repeated posts containing output.txt/zip... but I had cancelled the post using the link provided in the mail sent by [EMAIL PROTECTED] Now, to the point: Result of: nm --demangle libGravityCore.so | grep "Gravity::self" 0005e800 t Gravity::self() Result of: nm --demangl

Re: [CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

etween C++ compilers during your > OS upgrade, some of the symbols in your library may not be recognized > by the new compiler. > > Regards, > > Juan > > On Sat, Jul 12, 2008 at 7:34 AM, Philip Lowman <[EMAIL PROTECTED]> wrote: >> On Sat, Jul 12, 2008

Re: [CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

Yogesh M 2008/7/12 Philip Lowman <[EMAIL PROTECTED]>: > > On Sat, Jul 12, 2008 at 7:21 AM, Yogesh Marwaha <[EMAIL PROTECTED]> wrote: >> >> Hello, can someone figure out what I'm doing wrong. >> Here is the output I get when I attempt to compile: - >> ==

Re: [CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

] Error 2 make: *** [all] Error 2 = Thanks, -- Yogesh M 2008/7/10 Yogesh Marwaha <[EMAIL PROTECTED]>: > My project used to compile & link fine with cmake 2.4 on openSUSE 10.3. > Recently I upgraded to openSUSE 11, hence cmake 2.6, and now error is bein

[CMake] Problem linking to shared library (inside project) after upgrade to cmake 2.6

My project used to compile & link fine with cmake 2.4 on openSUSE 10.3. Recently I upgraded to openSUSE 11, hence cmake 2.6, and now error is being shown at link time. The project is mainly split in 3 sub-folders: - 1. library; generates GravityCore shared library 2. app; generates an executable w

Re: [CMake] problem setting CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX

On 29/01/2008, Brandon Van Every <[EMAIL PROTECTED]> wrote: > On Jan 29, 2008 10:42 AM, Yogesh Marwaha <[EMAIL PROTECTED]> wrote: > > Here is new CMakeLists.txt > > > > project (eSpy) > > cmake_minimum_required (VERSION 2.4.0) &

Re: [CMake] problem setting CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX

Ok, got it. Here is new CMakeLists.txt project (eSpy) cmake_minimum_required (VERSION 2.4.0) if(NOT CMAKE_BUILD_TYPE) set (CMAKE_BUILD_TYPE Release) endif(NOT CMAKE_BUILD_TYPE) if(NOT CMAKE_INSTALL_PREFIX) set (CMAKE_INSTALL_PREFIX "/usr/local") endif(NOT CMAKE_INS

Re: [CMake] problem setting CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX

All I want is the ability to change default values for CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX, i.e. if the user configures with only cmake .. If the user want it, these options should be changeable by supplying -DCMAKE_BUILD_TYPE and -DCMAKE_INSTALL_PREFIX to cmake Can you help me now, please.

[CMake] problem setting CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX

Hi I am having problem setting values for CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX Here is CMakeLists.txt in project root directory == project (eSpy) cmake_minimum_required (VERSION 2.4.0) set (CMAKE_BUILD_TYPE Release) set (CMAKE_INSTALL_PREFIX "/usr") find_packa