Re: [CMake] CMake Library Issues

2009-02-04 Thread Nick Ogden
Thanks for your help. It seems that the library cannot be compiled as static, when I tried it as dynamic it worked without a problem. I assume that this is due to the style includes as there wouldn't be a search path for a static library since it's part of the executable. Could anyone tell

Re: [CMake] CMake Library Issues

2009-02-04 Thread Michael Jackson
I don't think the style of include paths has anything to do with whether or not the library will compile as a static or dynamic library. What is the output of: MESSAGE(SERVER_SOURCE_DIR is ${SERVER_SOURCE_DIR}) Please post that to the list.

Re: [CMake] CMake Library Issues

2009-02-04 Thread Nick Ogden
OK, I finally found the problem. It seems that I was being silly and not being consistent with case in the project(X) call and the ${X_SOURCE_DIR} references. Everything is working as expected now, thanks for your help guys. On Wednesday 04 February 2009 12:19:11 Michael Jackson wrote: I

[CMake] CMake Library Issues

2009-02-03 Thread Nick Ogden
Hi there, I have a problem with using CMake to compile a library that I'm trying to use in an application that I'm writing. I have the following directory structure: src/ | CMakeLists.txt (1) | app/ | | CMakeLists.txt (2) | | (app source and headers) |

Re: [CMake] CMake Library Issues

2009-02-03 Thread Matthew Woehlke
Nick Ogden wrote: Hi there, I see you found the right list ;-). (And I will admit I was lazy and didn't read it before on kde-devel, which is why I'm just now answering your actual question.) I have a problem with using CMake to compile a library that I'm trying to use in an application

Re: [CMake] CMake Library Issues

2009-02-03 Thread Christopher Harvey
perhaps include_directories(..) That's how I do it. You can also print the ${SERVER_SOURCE_DIR} variable. MESSAGE(SERVER_SOURCE_DIR is ${SERVER_SOURCE_DIR}) Let me know if this works. Nick Ogden wrote: Hi there, I have a problem with using CMake to compile a library that I'm trying to use