Cross-platform open-source make system ()

Clang + MinGW Linking Issue

Hi All,

I've been trying out CMake for building C++ applications on Windows with Clang, using the MinGW headers/libraries. This works fine, except if I need to pull in non-default system libraries that are included with MinGW, such as libpsapi.a (psapi.lib for VS). For example, if I have the following CMakeLists.txt file:

project(pstest1)

add_executable(pstest1 pstest1.cpp)

target_link_libraries(pstest1 psapi)

This fails with a linker error:

Linking CXX executable pstest1.exe

c:\projects\cmake-2.8.8-win32-x86\bin\cmake.exe -E cmake_link_script CMakeFiles\pstest1.dir\link.txt --verbose=1

C:\projects\clang+llvm-3.1-i386-mingw32-EXPERIMENTAL\bin\clang++.exe CMakeFiles/pstest1.dir/pstest1.obj -o pst

est1.exe -lpsapi.lib

c:/mingw/bin/../lib/gcc/mingw32/4.6.2/../../../../mingw32/bin/ld.exe: cannot find -lpsapi.lib

collect2: ld returned 1 exit status

clang++: error: linker (via gcc) command failed with exit code 1 (use -v to see invocation)

mingw32-make[2]: *** [pstest1.exe] Error 1

mingw32-make[2]: Leaving directory `C:/projects/mingw-tests/pstest1/build'

mingw32-make[1]: *** [CMakeFiles/pstest1.dir/all] Error 2

mingw32-make[1]: Leaving directory `C:/projects/mingw-tests/pstest1/build'

mingw32-make: *** [all] Error 2

CMake seems to be using MSVC library naming conventions for Clang in MinGW mode, but also using the GCC-style -l flags for specifying libraries. If I replace

target_link_libraries(pstest1 psapi)

with

target_link_libraries(pstest1 "c:/MinGW/lib/libpsapi.a")

then everything works as expected (I got -lpsapi on the link line). Interestingly, everything also works correctly if I use the default mingw32-gcc.exe compiler instead of clang.exe. So this seems to be a CMake issue where it detects Clang but does not know how to properly pass GCC-style linker flags to Clang.

Any ideas?

Thanks,

Justin Holewinski

--

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

headers

jrosensw | 23 May 23:06

Need to prepend compiler with static analysis tool

Hey all,

   I'm trying to integrate insure++ with my cmake workspace.  The way insure
works is that you prepend the compiler with the insure executable.  For
example "/usr/bin/insure /usr/bin/g++ -o test test.cpp".  I've tried to
overrid CMAKE_CXX_COMPILER with these two executables, but it doesn't seem
like CMAKE likes this way.  I've also tried overriding CXX before running
"cmake" with this.  

   Can someone please tell me how to make this work?  Seems like it should
be simple enough, but I'm not finding the answer .

Thanks!

-JD

--
View this message in context: http://cmake.3232098.n2.nabble.com/Need-to-prepend-compiler-with-static-analysis-tool-tp7574176.html
Sent from the CMake mailing list archive at Nabble.com.
--

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

headers

Wiser, Tyson | 23 May 18:52

CMake for many interdependent libraries/executables

We currently have a fair number of libraries, executables and external
dependencies with fairly complicated dependencies.  As a simplified example,
consider the following diagram where dependencies flow from top to bottom (i.e.
higher depends on lower).

    exe1                 exe2
    | | \               /|  |
    | |  \             / |  |
    | |   \           /  |  |
    | |    \         /   |  |
    | |     \    libd    |  |
    | |      \   |  \    |  |
    | |       \  |   \   |  |
    | |       |  |    \  |  |
    | |       |  |     \ |  |
    | libc    |  |    libb  |
    |     \   |  |   /   |  |
    |      \  |  |  /    |  |
    |       \ |  | /     |  |
    |        \|  |/      |  |
    |         liba       |  |
    |        /           |  |
    |       /            |  |
     \     /             |  |
      \   /              |  |
      ext1               ext2

We don't modify external dependencies, but we do need to check them out and
build them before building a library or executable that depends on them.
Sometimes a developer will be working in a single library or executable.
Sometimes he will be working in multiple libraries and/or executables.  You can
imagine that for a new developer it becomes very complicated to know which
libraries and executables need to be checked out and in which order they need
to be built in order to satisfy all the dependencies.  Even established
developers that have all the necessary dependencies checked out and modify a
library have trouble knowing which libraries need to be rebuilt, and in what
order, for the change to propagate up to an executable.

In my ideal world, given that we can't change the dependency graph, I would
have a build system set up so that if I wanted to work on libb, I could simply
check it out and build it and it would automatically check out and build liba,
ext1, and ext2.  Then if I made changes to liba, building libb would notice the
change in liba and trigger that build first.  If I then decided that I needed
to work on exe2 I could check it out and build it and it would checkout and
build libd but use the existing libb, liba, ext1, and ext2 (triggering builds
as necessary if they are changed).  To further complicate the situation, we
need to build on both Linux and Windows.  So far we have been manually
maintaining makefiles on Linux and Visual Studio projects on Windows.

Phrased another way, I would like our build system to be able to:
1) Manage makefiles and Visual Studio solution/project files for us.
2) For a given library/executable, checkout and build missing dependencies.
3) For a given library/executable, build dependencies that have changed.
4) For a given executable, relink with changed dependent libraries (i.e. I
   change libb and build it and then build exe2, which relinks with libb).
5) When building a given library/executable for the first time, use existing
   dependencies within a given workspace (directory structure).

I have been investigation alternatives to our current system and CMake so far
seems to be the most promising.  I have never used CMake before, however, so I
am not entirely sure that I can make it match my ideal world, though I think it
can.  My current thoughts on how to accomplish this follow.

I know that CMake can handily manage #1.

I think that, given a directory structure similar to the following and setting
{TMP|STAMP|SOURCE|BINARY}_DIR appropriately, the ExternalProject module can
handle #2, #3 and #5.
  workspace-folder
    src
      exe2
      ext1
      ext2
      liba
      libb
      libd
    build
      exe2
      ext1
      ext2
      liba
      libb
      libd
    stamp
      exe2
      ext1
      ext2
      liba
      libb
      libd
    tmp
      exe2
      ext1
      ext2
      liba
      libb
      libd

I think that a "add_library(x UNKOWN IMPORTED)" and "set_property(TARGET x
PROPERTY IMPORTED_LOCATION y)" combination can handle #4.

Does this seem reasonable?  Is there a better way of doing it?  Would
maintaining the ExternalProject "superbuild" CMakeLists.txt files separately
from the regular CMakeLists.txt files be the recommended approach?

Thanks in advance for any help.
--

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

headers

Clifford Yapp | 23 May 15:44

Overriding the toplevel directory name in a TGZ package?

The CPack tool provides a variable CMAKE_INCLUDE_TOPLEVEL_DIRECTORY
option to control whether to set a toplevel directory in (say) a
tar.gz archive, but so far I have not been able to figure out if there
is a way to change this directory name to something not directly based
on the file name.  Trying to override CPACK_TOPLEVEL_DIRECTORY doesn't
seem to work.

Is there any way to get a tar.gz archive named (say)
NEW_PROJECT-3.1.1.tar.gz that unpacks into a toplevel directory simply
called PROJECT?

Thanks,
CY
--

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

headers

Nicolas Tisserand | 23 May 03:53

find_library search orders with CMAKE_PREFIX_PATH & CMAKE_FIND_ROOT_PATH

Hi all,

I am currently building a collection of inter-dependent libraries and tools, mostly cmake-built, all installed to a common staging directory.

I therefore need CMake find_library & find_package commands to search in the staging directory first, before inspecting the system.

Here's my problem: I can't get any combination of CMAKE_PREFIX_PATH or CMAKE_FIND_ROOT_PATH_MODE_* (in BOTH/NEVER/ONLY modes) to do this correctly, when find_library is given multiple names for the library.

It only works using CMAKE_PREFIX_PATH, or CMAKE_FIND_ROOT_PATH & CMAKE_FIND_ROOT_PATH_MODE=BOTH, provided that the name of the library present in the stage directory is the *first* of the library names list given to find_library.

It seems like the search order in such cases is as follows (in pseudo-code):

for each name in names

for dir in stage, system

if library_found(dir, name)

return dir, name

end

My use case would require the inner and outer loops to be swapped.

Please find attached a minimal test case illustrating my problem.

When running it on my Mac OS X 10.6 macbook, I get the following output:

==============================> cmake -DCMAKE_FIND_ROOT_PATH:PATH=/Users/nt/Hacks/cmake-find-png/stage -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY:STRING=ONLY ..

-- The C compiler identification is GNU

-- The CXX compiler identification is GNU

-- Checking whether C compiler has -isysroot

-- Checking whether C compiler has -isysroot - yes

-- Checking whether C compiler supports OSX deployment target flag

-- Checking whether C compiler supports OSX deployment target flag - yes

-- Check for working C compiler: /usr/bin/gcc

-- Check for working C compiler: /usr/bin/gcc -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Checking whether CXX compiler has -isysroot

-- Checking whether CXX compiler has -isysroot - yes

-- Checking whether CXX compiler supports OSX deployment target flag

-- Checking whether CXX compiler supports OSX deployment target flag - yes

-- Check for working CXX compiler: /usr/bin/c++

-- Check for working CXX compiler: /usr/bin/c++ -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

==============================> Looking for: png;png14

==============================> Found: /Users/nt/Hacks/cmake-find-png/stage/lib/libpng14.a

==============================> Looking for: png14;png

==============================> Found: /Users/nt/Hacks/cmake-find-png/stage/lib/libpng14.a

-- Configuring done

-- Generating done

-- Build files have been written to: /Users/nt/Hacks/cmake-find-png/build-ROOT_PATH_ONLY

/Users/nt/Hacks/cmake-find-png

==============================> cmake -DCMAKE_FIND_ROOT_PATH:PATH=/Users/nt/Hacks/cmake-find-png/stage -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY:STRING=BOTH ..

-- The C compiler identification is GNU

-- The CXX compiler identification is GNU

-- Checking whether C compiler has -isysroot

-- Checking whether C compiler has -isysroot - yes

-- Checking whether C compiler supports OSX deployment target flag

-- Checking whether C compiler supports OSX deployment target flag - yes

-- Check for working C compiler: /usr/bin/gcc

-- Check for working C compiler: /usr/bin/gcc -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Checking whether CXX compiler has -isysroot

-- Checking whether CXX compiler has -isysroot - yes

-- Checking whether CXX compiler supports OSX deployment target flag

-- Checking whether CXX compiler supports OSX deployment target flag - yes

-- Check for working CXX compiler: /usr/bin/c++

-- Check for working CXX compiler: /usr/bin/c++ -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

==============================> Looking for: png;png14

==============================> Found: /usr/X11R6/lib/libpng.dylib

==============================> Looking for: png14;png

==============================> Found: /Users/nt/Hacks/cmake-find-png/stage/lib/libpng14.a

-- Configuring done

-- Generating done

-- Build files have been written to: /Users/nt/Hacks/cmake-find-png/build-ROOT_PATH_BOTH

/Users/nt/Hacks/cmake-find-png

==============================> cmake -DCMAKE_FIND_ROOT_PATH:PATH=/Users/nt/Hacks/cmake-find-png/stage -DCMAKE_FIND_ROOT_PATH_MODE_LIBRARY:STRING=NEVER ..

-- The C compiler identification is GNU

-- The CXX compiler identification is GNU

-- Checking whether C compiler has -isysroot

-- Checking whether C compiler has -isysroot - yes

-- Checking whether C compiler supports OSX deployment target flag

-- Checking whether C compiler supports OSX deployment target flag - yes

-- Check for working C compiler: /usr/bin/gcc

-- Check for working C compiler: /usr/bin/gcc -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Checking whether CXX compiler has -isysroot

-- Checking whether CXX compiler has -isysroot - yes

-- Checking whether CXX compiler supports OSX deployment target flag

-- Checking whether CXX compiler supports OSX deployment target flag - yes

-- Check for working CXX compiler: /usr/bin/c++

-- Check for working CXX compiler: /usr/bin/c++ -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

==============================> Looking for: png;png14

==============================> Found: /usr/X11R6/lib/libpng.dylib

==============================> Looking for: png14;png

==============================> Found: /usr/X11R6/lib/libpng.dylib

-- Configuring done

-- Generating done

-- Build files have been written to: /Users/nt/Hacks/cmake-find-png/build-ROOT_PATH_NEVER

/Users/nt/Hacks/cmake-find-png

==============================> cmake -DCMAKE_PREFIX_PATH:PATH=/Users/nt/Hacks/cmake-find-png/stage ..

-- The C compiler identification is GNU

-- The CXX compiler identification is GNU

-- Checking whether C compiler has -isysroot

-- Checking whether C compiler has -isysroot - yes

-- Checking whether C compiler supports OSX deployment target flag

-- Checking whether C compiler supports OSX deployment target flag - yes

-- Check for working C compiler: /usr/bin/gcc

-- Check for working C compiler: /usr/bin/gcc -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Checking whether CXX compiler has -isysroot

-- Checking whether CXX compiler has -isysroot - yes

-- Checking whether CXX compiler supports OSX deployment target flag

-- Checking whether CXX compiler supports OSX deployment target flag - yes

-- Check for working CXX compiler: /usr/bin/c++

-- Check for working CXX compiler: /usr/bin/c++ -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

==============================> Looking for: png;png14

==============================> Found: /usr/X11R6/lib/libpng.dylib

==============================> Looking for: png14;png

==============================> Found: /Users/nt/Hacks/cmake-find-png/stage/lib/libpng14.a

-- Configuring done

-- Generating done

-- Build files have been written to: /Users/nt/Hacks/cmake-find-png/build-PREFIX

/Users/nt/Hacks/cmake-find-png

Any thoughts?

Thanks for making such a useful cross-platform build tool.

Attachment (cmake-find-png.zip): application/zip, 1558 bytes

--

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

headers

Robert Dailey | 22 May 20:49

Undefine a project()

Hi,

I was wondering if there is a way to undefined a project(). I want to do this to prevent projects from being included in a solution when I generate for Visual Studio. Example:

project( A )

add_executable( A a.cpp )

project( B )

add_executable( B b.cpp )

add_executable( C c.cpp )

I don't want B to be in A's solution when I open A.sln. I'm assuming this is the behavior, unless project(B) call cancels out project(A)?

Also, I don't want project C to appear in either A or B solutions.

The reason why I'm doing this is because I have setup my CMake scripts to allow a solution file to be generated for executables (so I can open each executable solution in different instances of visual studio, with ONLY that executable + dependency projects in it). However, since sometimes multiple executable projects can be defined in the same directory, or other libraries that aren't a dependency of that executable, I do not want those to be included in the project().

--

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

headers

Cristian Cocheci | 22 May 14:08

Select a project for building only for a specific configuration

I have seen this question asked before, but did not find any good answer for it, so I was hoping that meanwhile someone might have found a good solution.

I need to select one of the projects for building in our Visual Studio solution (that contains ~ 20 total projects) only in a certain configuration (e.g. Release). Our nightly builds run on a Jenkins build server so I need CMake to output the generators with that specific project selected for building only in Release. Has anyone found a good way to do this?

Thanks,

Cristian

--

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

headers

Marmot Ken | 22 May 03:07

the list parameter passed to function

here is the function :

FUNCTION( Append_headers_to_src_list src_list_out src_list_in header_file_path_in )
    MESSAGE( src_list_in " : ${src_list_in}" )
    FILE( GLOB_RECURSE TEMP_LIST ${header_file_path_in}/*.h )
    SET( ${src_list_out} ${src_list_in} ${TEMP_LIST} PARENT_SCOPE )
ENDFUNCTION( Append_headers_to_src_list

here is the place where the function is invoked:

AUX_SOURCE_DIRECTORY( . SRC_LIST )
MESSAGE( SRC_LIST " : ${SRC_LIST} " )

Append_headers_to_src_list( SRC_LIST ${SRC_LIST} ${CMAKE_SOURCE_DIR}/include/test )

here is output　：　

SRC_LIST : ./a.cpp;./c.cpp;./main.cpp
src_list_in : ./a.cpp

Output expected :

SRC_LIST : ./a.cpp;./c.cpp;./main.cpp
src_list_in : ./a.cpp

Ｑｕｅｓｔｉｏｎ：
　     <1> how to get expected Output ?
        <2> why ?

Thanks.

--

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

headers

David Aiken | 21 May 21:01

generating gettext runtime environment on OSX Lion (.7z attachment)

The original message was held for review because the .zip attachment exceeded the 40k limit.

This is using .7z compression, which gets well under the 40k limit. Ez7z was used to generate it

on OSX Lion.

From: David Aiken <david_aiken-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: "cmake-wChDC6UyXvPYtjvyW6yDsg@public.gmane.org" <cmake-wChDC6UyXvPYtjvyW6yDsg@public.gmane.org>
Sent: Monday, May 21, 2012 11:48:27 AM
Subject: generating gettext runtime environment on OSX Lion

hi all..

I'm trying to generate the runtime files necessary to support calls to gettext() on OSX Lion 10.7.4 with:

gettext 0.18.1

xcode 4.3.2

cmake 2.8.7

but so far no luck. I've attached a simple (well.. as simple as i could make it) project.. the binaries build on my box, but the translation files do not.

The cmake log is:

The C compiler identification is GNU 4.2.1

The CXX compiler identification is GNU 4.2.1

Checking whether C compiler has -isysroot

Checking whether C compiler has -isysroot - yes

Checking whether C compiler supports OSX deployment target flag

Checking whether C compiler supports OSX deployment target flag - yes

Check for working C compiler using: Xcode

Check for working C compiler using: Xcode -- works

Detecting C compiler ABI info

Detecting C compiler ABI info - done

Checking whether CXX compiler has -isysroot

Checking whether CXX compiler has -isysroot - yes

Checking whether CXX compiler supports OSX deployment target flag

Checking whether CXX compiler supports OSX deployment target flag - yes

Check for working CXX compiler using: Xcode

Check for working CXX compiler using: Xcode -- works

Detecting CXX compiler ABI info

Detecting CXX compiler ABI info - done

Found Gettext: /opt/local/bin/msgmerge (found version "0.18.1")

Found LIBINTL: /usr/local/lib/libintl.dylib

Configuring done

Generating done

and the build log for ALL_BUILD is:

Build target ZERO_CHECK

PhaseScriptExecution "CMake Rules" build/translation.build/Debug/ZERO_CHECK.build/Script-CC986575905544D58E84845A.sh

cd /Volumes/untitled/test/translation

/bin/sh -c /Volumes/untitled/test/translation/build/translation.build/Debug/ZERO_CHECK.build/Script-CC986575905544D58E84845A.sh

echo ""

make -f /Volumes/untitled/test/translation/build/CMakeScripts/ReRunCMake.make

make[1]: `CMakeFiles/cmake.check_cache' is up to date.

Build target translations_2

PhaseScriptExecution "CMake Rules" build/utils/translation.build/Debug/translations_2.build/Script-C63B422217D34C39BB5AFCAA.sh

cd /Volumes/untitled/test/translation

/bin/sh -c /Volumes/untitled/test/translation/build/utils/translation.build/Debug/translations_2.build/Script-C63B422217D34C39BB5AFCAA.sh

make: *** No rule to make target `/Volumes/untitled/test/translation/utils/utils.pot', needed by `/Volumes/untitled/test/translation/build/utils/fr_CA.gmo'. Stop.

Command /bin/sh failed with exit code 2

Build target utils

CompileC build/utils/translation.build/Debug/utils.build/Objects-normal/x86_64/utils.o utils/src/utils.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler

cd /Volumes/untitled/test/translation

setenv LANG en_US.US-ASCII

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch x86_64 -fmessage-length=0 -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes -Wno-return-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wformat -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wno-unused-variable -Wunused-value -Wno-uninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-sign-compare -Wno-shorten-64-to-32 -Wno-newline-eof -Wc++11-extensions "-DCMAKE_INTDIR=\"Debug\"" -Dutils_EXPORTS -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk -fasm-blocks -Wdeprecated-declarations -Winvalid-offsetof -mmacosx-version-min=10.7 -g -Wno-conversion -Wno-sign-conversion -I/Volumes/untitled/test/translation/build/utils/Debug/include -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/usr/local/include -I/Volumes/untitled/test/translation/build/utils/translation.build/Debug/utils.build/DerivedSources/x86_64 -I/Volumes/untitled/test/translation/build/utils/translation.build/Debug/utils.build/DerivedSources -Wmost -Wno-four-char-constants -Wno-unknown-pragmas -F/Volumes/untitled/test/translation/build/utils/Debug -fPIC -MMD -MT dependencies -MF /Volumes/untitled/test/translation/build/utils/translation.build/Debug/utils.build/Objects-normal/x86_64/utils.d --serialize-diagnostics /Volumes/untitled/test/translation/build/utils/translation.build/Debug/utils.build/Objects-normal/x86_64/utils.dia -c /Volumes/untitled/test/translation/utils/src/utils.cpp -o /Volumes/untitled/test/translation/build/utils/translation.build/Debug/utils.build/Objects-normal/x86_64/utils.o

Ld build/utils/Debug/libutils.dylib normal x86_64

cd /Volumes/untitled/test/translation

setenv MACOSX_DEPLOYMENT_TARGET 10.7

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -arch x86_64 -dynamiclib -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk -L/Volumes/untitled/test/translation/build/utils/Debug -F/Volumes/untitled/test/translation/build/utils/Debug -filelist /Volumes/untitled/test/translation/build/utils/translation.build/Debug/utils.build/Objects-normal/x86_64/utils.LinkFileList -install_name /Volumes/untitled/test/translation/build/utils/Debug/libutils.dylib -mmacosx-version-min=10.7 -dynamiclib -Wl,-headerpad_max_install_names -single_module -o /Volumes/untitled/test/translation/build/utils/Debug/libutils.dylib

PhaseScriptExecution "CMake PostBuild Rules" build/utils/translation.build/Debug/utils.build/Script-28DDF846B34C4ADCAF3FFA1D.sh

cd /Volumes/untitled/test/translation

/bin/sh -c /Volumes/untitled/test/translation/build/utils/translation.build/Debug/utils.build/Script-28DDF846B34C4ADCAF3FFA1D.sh

echo "Depend check for xcode"

Depend check for xcode

cd /Volumes/untitled/test/translation/build && make -C /Volumes/untitled/test/translation/build -f /Volumes/untitled/test/translation/build/CMakeScripts/XCODE_DEPEND_HELPER.make PostBuild.utils.Debug

make: *** [utils_buildpart_0] Interrupt: 2

Build target translations_1

PhaseScriptExecution "CMake Rules" build/exe/translation.build/Debug/translations_1.build/Script-04B354006AFB4F308C29CC4A.sh

cd /Volumes/untitled/test/translation

/bin/sh -c /Volumes/untitled/test/translation/build/exe/translation.build/Debug/translations_1.build/Script-04B354006AFB4F308C29CC4A.sh

make: *** No rule to make target `/Volumes/untitled/test/translation/exe/exe.pot', needed by `/Volumes/untitled/test/translation/build/exe/fr_CA.gmo'. Stop.

Command /bin/sh failed with exit code 2

any help would be appreciated.

thanks!

Attachment (translation.7z): application/octet-stream, 8 KiB

--

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

headers

NoRulez | 21 May 18:39

CPack: Installing applications in separate folders (NSIS)

Hi,

I know that the install commands collect files and copy them into the temporary cpack directory for the
specified generator.
How is it possible to install an application for example into those folders:
C:\myapp
C:\somefolder

I defined 'Var CustomDir="C:\somefolder"' in the NSIS template.

When I then use the following in the CMakeLists.txt:
install(FILES ${CMAKE_SOURCE_DIR}/somefolder/myfile.txt DESTINATION $CustomDir)

Then the files are installed in _CPACK_PACKAGES/NSIS/myproject_1.0.0.1/$CustomDir.
The generated project.nsi has the content: $INSTDIR\$CustomDir\...

How can I avoid that $INSTDIR\ is added, or did I need to use the install command in a different way?

Thanks in advance

Best Regards
NoRulez

--

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

headers

Nicholas Yue | 21 May 10:37

Packaging : Debug + Release together

Hi,

     I can build debug and release code by setting the CMAKE_BUILD_TYPE 
variable.

     What is the recommend process/workflow if I wish to 
build/install/package both the Debug and Release build into a single 
e.g. RPM, as part of an automated process (e.g. nightly build) ?

     How will CPack find the different builds for packaging ?

Regards

-- 
Nicholas Yue
Graphics - RenderMan, Visualization, OpenGL, HDF5
Custom Dev - C++ porting, OSX, Linux, Windows
Management - Recruitment, career management
http://www.proceduralinsight.com/
http://au.linkedin.com/in/nicholasyue

--

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

370	May 2012
316	April 2012
385	March 2012
459	February 2012
579	January 2012
489	December 2011
721	November 2011
583	October 2011
452	September 2011
405	August 2011
428	July 2011
584	June 2011
496	May 2011
424	April 2011
581	March 2011
694	February 2011
745	January 2011
529	December 2010
591	November 2010
579	October 2010
642	September 2010
613	August 2010
797	July 2010
586	June 2010
542	May 2010
457	April 2010
747	March 2010
544	February 2010
640	January 2010
651	December 2009
644	November 2009
600	October 2009
648	September 2009
591	August 2009
563	July 2009
739	June 2009
618	May 2009
732	April 2009
978	March 2009
620	February 2009
516	January 2009
575	December 2008
696	November 2008
584	October 2008
632	September 2008
576	August 2008
647	July 2008
451	June 2008
705	May 2008
538	April 2008
671	March 2008
620	February 2008
665	January 2008
789	December 2007
824	November 2007
639	October 2007
552	September 2007
579	August 2007
610	July 2007
525	June 2007
536	May 2007
370	April 2007
411	March 2007
267	February 2007
363	January 2007
293	December 2006
355	November 2006
416	October 2006
423	September 2006
512	August 2006
484	July 2006
513	June 2006
400	May 2006
243	April 2006
307	March 2006
330	February 2006
270	January 2006

Mon	Tue	Wed	Thu	Fri	Sat	Sun

	1	2	3	4	5	6
7	8	9	10	11	12	13
14	15	16	17	18	19	20
21	22	23	24	25	26	27
28	29	30	31