Re: [CMake] How to link against a .dll with cmake?

2010-07-25 Thread Andreas Pakulat
On 25.07.10 00:57:14, John Drescher wrote:
  mingw can link using a .dll
 
 
 I do not have much mingw experience but I have around 15 of windows
 and Visual Studio experience. With Visual Studio you absolutely do not
 link your application with .dlls. You use import libs with a .lib
 extension the same way you do with a static lib. This import lib is
 not a static lib however its much smaller. During the application load
 process .dlls linked using import libraries are automatically loaded.
 This is not the only way to use .dlls you can use them also without
 linking but there is much more work in that.

Same goes for mingw, but it has a way of extracting the import library
from a .dll, see
http://www.stats.uwo.ca/faculty/murdoch/software/compilingDLLs/existingDLL.html

Andreas

-- 
You are fairminded, just and loving.
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] How to link against a .dll with cmake?

2010-07-25 Thread andy fillebrown
The documentation is not current.  Mingw can now link directly to a
.dll.  See the direct linking to a dll section here ...
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu-linker/win32.html


On Sun, Jul 25, 2010 at 4:35 AM, Andreas Pakulat ap...@gmx.de wrote:
 On 25.07.10 00:57:14, John Drescher wrote:
  mingw can link using a .dll
 

 I do not have much mingw experience but I have around 15 of windows
 and Visual Studio experience. With Visual Studio you absolutely do not
 link your application with .dlls. You use import libs with a .lib
 extension the same way you do with a static lib. This import lib is
 not a static lib however its much smaller. During the application load
 process .dlls linked using import libraries are automatically loaded.
 This is not the only way to use .dlls you can use them also without
 linking but there is much more work in that.

 Same goes for mingw, but it has a way of extracting the import library
 from a .dll, see
 http://www.stats.uwo.ca/faculty/murdoch/software/compilingDLLs/existingDLL.html

 Andreas

 --
 You are fairminded, just and loving.
 ___
 Powered by www.kitware.com

 Visit other Kitware open-source projects at 
 http://www.kitware.com/opensource/opensource.html

 Please keep messages on-topic and check the CMake FAQ at: 
 http://www.cmake.org/Wiki/CMake_FAQ

 Follow this link to subscribe/unsubscribe:
 http://www.cmake.org/mailman/listinfo/cmake

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


[CMake] Make Nightly build tests.

2010-07-25 Thread Björn Piltz
Hi all,
I'm quoting my question here:
http://stackoverflow.com/questions/3290280/cmake-and-ctest-how-to-make-target-nightly-actually-build-the-tests

It's a well known problem that executing make test doesn't build the
tests as discussed here. As suggested, the problem can be partly
solved with the artificial target check. I want to know how I can
force building of tests when i call make Nightly.

What I've done so far:

  add_custom_target(buildtests)
  add_custom_target(check COMMAND ctest)
  add_dependencies(check buildtests)
  add_dependencies(Nightly buildtests)

  add_dependencies(buildtests Test1)
  ...
  add_dependencies(buildtests TestN)

Now make check builds an runs the tests, but make Nightly

builds the tests
updates the repo to CTEST_NIGHTLY_START_TIME
builds all other targets
runs the (now outdated) tests

I'd be greatful for any suggestions!
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Re: [CMake] Debug/Release configurations for codeblocks ?

2010-07-25 Thread Alexander Neundorf
On Thursday 22 July 2010, Carlos wrote:
 Hello,

 It seems the debug/release default configuration are only built for VStudio
 suites.
 Anyway I am trying to simulated such for the codeblocks IDE, this is how I
 did my CMakeLists.txt :

 project( myapp )

 add_executable( Release WIN32 ${my_src_files} )
 target_link_libraries( Release  ${my_libs} )
 set_target_properties( Release PROPERTIES OUTPUT_NAME myappname )

 add_executable( Debug ${my_src_files} )
 target_link_libraries( Debug ${my_libs_dbg} )
 set_source_files_properties( Debug PROPERTIES COMPILE_DEFINITIONS  etc
  )
 set_target_properties( Debug PROPERTIES OUTPUT_NAME myappname_dbg  etc
  )


 Actually this works pretty fine but :

 Is that the right way to simulate VS build configurations ?

Hmm, the Codeblocks generator is makefile-based.
Each makefile-based buildtree builds only one configuration.
If you want multiple configurations, create one buildtree for each 
configuration (each with its own C::B project file).

 Is there any chance this conflicts with the VS generator ?

 Other misc question :

 What are the xxx/fast configurations in codeblocks ?

They are for building the respective target, but without checking whether the 
dependent targets are up-to-date (i.e. if you build A and A links against 
B, A/fast will only check what needs to be built for A, but not check all 
source files of B whether they have to be rebuild. This saves the time for 
checking the dependencies).

Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] cross-compiling: Add Support for IAR compiler

2010-07-25 Thread Alexander Neundorf
On Thursday 22 July 2010, Hassan Mansouri wrote:
 Hi,
 I am trying to do cross-compiling with CMake for IAR compiler (ARM).
 My main problem with the current CMake 2.8.2 is the complain about -c 
 option from IAR compiler. IAR compiler does not accept -c as input C  file
 and the sysntax is CC filename.c [options]. How can I tell  CMake not to
 put -c when calling the external compiler when it's IAR?

 There is a link for supporting IAR compiler in CMake at:
 http://www.cmake.org/Bug/view.php?id=10176 but I don't know how to apply
 the changes.
 Can anybody tell me what is the conclusion and how can I apply the required
 patches to CMake? This discussion is for CMake 2.6, is this fixed in newer
 version of CMake?

I plan to finish the work on this in the next weeks, and I'm happy if you can 
help me with that. Let's continue the discussion in the bugtracker in the 
next days.

Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] CPack: Detecting if to build DEB/RPM packages

2010-07-25 Thread Alexander Neundorf
On Thursday 22 July 2010, Eric Noulard wrote:
 2010/7/22 Olaf van der Spek olafvds...@gmail.com:
  On Thu, Jul 22, 2010 at 11:08 PM, Eric Noulard eric.noul...@gmail.com 
wrote:
  Yes it should, if ever the proposed patch
  http://public.kitware.com/Bug/view.php?id=10292
  is merged as-is.
 
  What's the delay?

 I do not have an authoritative answer,
 I'm not Kitware employee just a bare CMake contributor.

Don't you have commit access ?

Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] cmake generators on windows: nmake versus jom

2010-07-25 Thread Alexander Neundorf
On Thursday 22 July 2010, Verweij, Arjen wrote:
 Brad,

 I found another repository with jom binaries. It works fine with 0.9.4.

 Apparently the original link I used to download JOM was ancient.

Here ( 
http://www.cmake.org/Wiki/CMake_Generator_Specific_Information#Makefile_generators
 ) 
is some documentation about the available generators.
Feel free to add some notes about the jom generator there :-)
It's a wiki, you can simply get a login.

Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] CPack: Detecting if to build DEB/RPM packages

2010-07-25 Thread Eric Noulard
2010/7/25 Alexander Neundorf a.neundorf-w...@gmx.net:
 On Thursday 22 July 2010, Eric Noulard wrote:
 2010/7/22 Olaf van der Spek olafvds...@gmail.com:
  On Thu, Jul 22, 2010 at 11:08 PM, Eric Noulard eric.noul...@gmail.com
 wrote:
  Yes it should, if ever the proposed patch
  http://public.kitware.com/Bug/view.php?id=10292
  is merged as-is.
 
  What's the delay?

 I do not have an authoritative answer,
 I'm not Kitware employee just a bare CMake contributor.

 Don't you have commit access ?

Yes I do.

But I was granted commit access for CPackRPM and I don't want
to abuse my commit trust on every patch I found OK :-)

Switching cmake-devel in order to go on with this discussion
on CPackDeb related patches?


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] CPack: Detecting if to build DEB/RPM packages

2010-07-25 Thread Olaf van der Spek
On Sun, Jul 25, 2010 at 7:13 PM, Eric Noulard eric.noul...@gmail.com wrote:
 Switching cmake-devel in order to go on with this discussion
 on CPackDeb related patches?

I don't see cmake-devel at http://www.cmake.org/cmake/help/mailing.html
How come?

Olaf
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] CPack: Detecting if to build DEB/RPM packages

2010-07-25 Thread Eric Noulard
2010/7/25 Olaf van der Spek olafvds...@gmail.com:
 On Sun, Jul 25, 2010 at 7:13 PM, Eric Noulard eric.noul...@gmail.com wrote:
 Switching cmake-devel in order to go on with this discussion
 on CPackDeb related patches?

 I don't see cmake-devel at http://www.cmake.org/cmake/help/mailing.html
 How come?

Don't know.

It is not listed there but it is accessible here:
http://www.cmake.org/mailman/listinfo/cmake-developers

The list is usually used by CMake developers/contributos to
discuss issue which would usually annoy normal CMake users :-)

- Like how use git for doing that?
- How come my commit is refused by git with this cryptic message blah blah...


-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


Re: [CMake] cross compiler c166.exe

2010-07-25 Thread Alexander Neundorf
On Tuesday 13 July 2010, Thomas Hafner wrote:
 Hello,

 CMake is complaining about missing settings:
 | CMake Error at C:/Programme/CMake
 | 2.8/share/cmake-2.8/Modules/CMakeRCInformation.cmake:22
 | (GET_FILENAME_COMPONENT): get_filename_component called with incorrect
 | number of arguments Call Stack (most recent call first):
 |   C:/Programme/CMake
 | 2.8/share/cmake-2.8/Modules/Platform/Windows-cl.cmake:32
 | (ENABLE_LANGUAGE) C:/Programme/CMake
 | 2.8/share/cmake-2.8/Modules/CMakeCInformation.cmake:58 (INCLUDE)
 | CMakeLists.txt:2 (PROJECT)
 |
 |
 | CMake Error: CMAKE_RC_COMPILER not set, after EnableLanguage
 | CMake Error: your C compiler: cl was not found.   Please set
 | CMAKE_C_COMPILER to a valid compiler path or name. CMake Error: Internal
 | CMake error, TryCompile configure of cmake failed -- Check for working C
 | compiler: cl -- broken
 | CMake Error at C:/Programme/CMake
 | 2.8/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE): The C
 | compiler cl is not able to compile a simple test program.
 |
 |   It fails with the following output:
 |
 |
 |
 |
 |
 |   CMake will not be able to correctly generate this project.
 | Call Stack (most recent call first):
 |   CMakeLists.txt:12 (project)
 |
 |
 | CMake Error: your C compiler: cl was not found.   Please set
 | CMAKE_C_COMPILER to a valid compiler path or name. CMake Error: your CXX
 | compiler: cl was not found.   Please set CMAKE_CXX_COMPILER to a valid
 | compiler path or name.

 I've already taken the Article about CMake Cross Compiling
 http://www.cmake.org/Wiki/CMake_Cross_Compiling into consideration and

 have coded this:
 | include(CMakeForceCompiler)
 | set(ISOAGLIB_C166INSTALLATIONDIR c:/c166)
 | set(CMAKE_SYSTEM_NAME Generic)
 | cmake_force_c_compiler(${ISOAGLIB_C166INSTALLATIONDIR}/bin/c166.exe
 | GNU)
 | cmake_force_cxx_compiler(${ISOAGLIB_C166INSTALLATIONDIR}/bin/c166.exe
 | GNU) set(CMAKE_C_COMPILER,
 | ${ISOAGLIB_C166INSTALLATIONDIR}/bin/c166.exe) set(CMAKE_CXX_COMPILER,
 | ${ISOAGLIB_C166INSTALLATIONDIR}/bin/c166.exe) message(STATUS (compiler
 | ${ISOAGLIB_C166INSTALLATIONDIR}/bin/c166.exe)) set(CMAKE_FIND_ROOT_PATH,
 |   ${ISOAGLIB_C166INSTALLATIONDIR}/include.cpp,
 |   ${ISOAGLIB_C166INSTALLATIONDIR}/include,
 |   ${ISOAGLIB_C166INSTALLATIONDIR}/lib)
 | set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
 | set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
 | set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)

 What's wrong with it? What's the compiler id? CMake does not know my
 cross compiler so far. Which compiler id should I take? How can I tell
 CMake, that there's no resource compiler? Why is CMake looking for a
 compiler called cl, although my compiler is c166.exe from TASKING
 Inc.?

You are not only doing cross compiling, additionally you are using a toolchain 
which is not yet supported by cmake, so this has to be added.
I.e. the toolchain has to be recognized, and a Modules/Compiler/Tasking.cmake 
or something like this needs to be added.

Please put this in a new bug in the bug tracker at 
http://public.kitware.com/Bug/my_view_page.php , then we can continue there.

Alex
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


[CMake] Can't configure for Visual C++ 2010 Express using CMake 2.8.2

2010-07-25 Thread Tron Thomas
I am running the 64-bit version of Windows 7 Enterprise, and I have been 
using CMake 2.8.1 to configure my cross platform project to build with 
the express version of Visual C++ 9 2008.


I recently install the express version of Visual C++ 2010 on the system, 
and upgraded to CMake 2.8.2.  Now when I go to configure my project for 
Windows I get the following error output:


CMake Error at 
3rdParty/Windows/Applications/CMake/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:70 
(MESSAGE):

  Could NOT find OpenAL (missing: OPENAL_INCLUDE_DIR)
Call Stack (most recent call first):
  
3rdParty/Windows/Applications/CMake/share/cmake-2.8/Modules/FindOpenAL.cmake:101 
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)

  Engine/CMakeLists.txt:7 (find_package)

I don't know why CMake is not able to find the OpenAL include 
directory.  My main CMakeLists.txt script checks against WIN32 to 
include an additional Windows specific script that sets the 
CMAKE_INCLUDE_PATH variable to the location for all needed header files 
(including OpenAL headers).


What is needed so that CMake can configure my project correctly for 
Visual C++ 2010 Express?


___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake