Re: [CMake] How to generate a non-standard platform and non-standard project file with the Visual studio generator
ualDe vice\lib;$(MLSDK)\lib\win64 $(ProjectDir)\$ml_asset_folder$ $mlsdkpath$ $host_release_certificate$ $ml_extra_build_options$ $host_release_full_spec$ $(MLSDK);$(PATH) mabu $(MLProjectFile) MLSDK="$(MLSDK)" -t msvc-$msvcversion$_release -v VCDIR="$(VCInstallDir) $(MLExtraBuildOption) mabu $(MLProjectFile) MLSDK="$(MLSDK)" -t msvc-$msvcversion$_release -r -v VCDIR="$(VCInstallDir) $(MLExtraBuildOption) mabu $(MLProjectFile) MLSDK="$(MLSDK)" -t msvc-$msvcversion$_release -c -v VCDIR="$(VCInstallDir) $(MLExtraBuildOption) $host_release_preprocessor_defines$ $host_release_include_paths$ $host_release_packagefile$ $host_release_outputdir$ $(ProjectDir)\$(IntDir) $(IntDir)\$host_release_outputfile$ WindowsLocalDebugger false PATH=$(MLSDK)\VirtualDevice\bin;$(MLSDK)\VirtualDe vice\lib;$(MLSDK)\lib\win64 $(ProjectDir)\$ml_asset_folder$ $mlprojsources$ $mlprojincludes$ $mlprojresources$ $mlotherfiles$ I've been thinking about several alternatives. My first thought was to make modifications to the Visual Studio generator to support passing in the Platform and the options that I need but after reviewing the generator code, it looks like a monumental task, especially considering how many changes there are from a typical Visual Studio project file. The second thought I had was to post process the build file using CMake string replace or python. This seems like it would be much more manageable but before I went down that path I wanted to see if there is a more obvious way that is in better alignment with the CMake approach. I've even been asking myself if it makes sense to use CMake for this at all or is it just too far outside of the typical use cases. Any suggestions on the best path forward would be greatly appreciated. Thanks, Jeff -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
[CMake] How to generate a non-standard platform and non-standard project file with the Visual studio generator
the generator code, it looks like a monumental task, especially considering how many changes there are from a typical Visual Studio project file. The second thought I had was to post process the build file using CMake string replace or python. This seems like it would be much more manageable but before I went down that path I wanted to see if there is a more obvious way that is in better alignment with the CMake approach. I've even been asking myself if it makes sense to use CMake for this at all or is it just too far outside of the typical use cases. Any suggestions on the best path forward would be greatly appreciated. Thanks, Jeff -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake
Re: [CMake] Hyperlink to build URL
Hi Jc, That's exactly what I was looking for. Thank you! ~Jeff On Tue, Jun 17, 2014 at 8:27 PM, Jean-Christophe Fillion-Robin < jchris.filli...@kitware.com> wrote: > Hi Jeff, > > If you upload a file having extension .url containing the url, it will be > associated with your build by presenting a package icon allowing to then > open the corresponding link. > > For more details, see section "File upload" in this article [1] > > For an example see [2] > > Hth > Jc > > [1] http://www.kitware.com/source/home/post/59 > [2] > https://github.com/Slicer/Slicer/blob/57f14d0d233ee103e365161cfc0b3962df0bc203/CMake/MIDASCTestUploadURL.cmake#L69 > > > > > On Wed, Jun 11, 2014 at 1:13 PM, Jeff Mills wrote: > >> Hello, >> >> Our build system makes use of CMake/CDash and Jenkins. I'd like to be >> able to add a link in CDash for the URL to the associated Jenkins build, so >> that it is easy for the developers to move between the two. So far my >> attempts have not been successful. I've tried attaching the url in a note >> file but is doesn't display as a clickable link. Adding the >> tags around the link in the configure log also doesn't work. Is there way >> to add the link that I am missing? I've tried searching the documentation >> and the list archives. Any help would be appreciated. >> >> Cheers, >> Jeffrey Mills >> Transpire Inc. >> >> -- >> >> Powered by www.kitware.com >> >> Please keep messages on-topic and check the CMake FAQ at: >> http://www.cmake.org/Wiki/CMake_FAQ >> >> Kitware offers various services to support the CMake community. For more >> information on each offering, please visit: >> >> CMake Support: http://cmake.org/cmake/help/support.html >> CMake Consulting: http://cmake.org/cmake/help/consulting.html >> CMake Training Courses: http://cmake.org/cmake/help/training.html >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Follow this link to subscribe/unsubscribe: >> http://www.cmake.org/mailman/listinfo/cmake >> > > > > -- > +1 919 869 8849 > -- Jeffrey Mills Transpire Inc. +1 (253) 857 1056 x102 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
[CMake] Hyperlink to build URL
Hello, Our build system makes use of CMake/CDash and Jenkins. I'd like to be able to add a link in CDash for the URL to the associated Jenkins build, so that it is easy for the developers to move between the two. So far my attempts have not been successful. I've tried attaching the url in a note file but is doesn't display as a clickable link. Adding the tags around the link in the configure log also doesn't work. Is there way to add the link that I am missing? I've tried searching the documentation and the list archives. Any help would be appreciated. Cheers, Jeffrey Mills Transpire Inc. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] PDB generation
On Wed, May 21, 2014 at 12:21 PM, Scott Aron Bloom <
scott.bl...@onshorecs.com> wrote:
> At some point in the 2.8 lifecycle, the choice was made to no longer
> copy the .pdb files on windows builds with the .lib that is generated.
>
>
>
> I found a note somewhere, that there was “good” reasoning for it.. And in
> general, I agree, for many applications you don’t need the pdb files for
> static libraries.
>
>
>
> However, if the target of your project IS a static library that you supply
> to customers for integration into their toosl, you NEED to supply the pdb
> otherwise they are stuck getting the “pdb not found” warning message.
>
FWLIW, here's how I handle it:
a) Provide INSTALL_PDB option for my project which defaults to ON for
Windows
b) track which pdb files might be available by updating install_bin_pdb and
install_modules_pdb with targets that need to be copied
e.g., for some executable target named by the pgm variable:
SET(install_bin_pdb ${install_bin_pdb} ${PROJECT_BINARY_DIR}/${pgm}.pdb)
c) with my other install logic
IF(INSTALL_PDB)
INSTALL(FILES ${install_bin_pdb}
DESTINATION bin
CONFIGURATIONS RelWithDebInfo Debug)
INSTALL(FILES ${install_modules_pdb}
DESTINATION modules
CONFIGURATIONS RelWithDebInfo Debug)
ENDIF()
>
> Is there any hope chance of bringing this back?
>
> Scott
>
> --
>
> Powered by www.kitware.com
>
> Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
>
> Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
>
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
>
--
Born in Roswell... married an alien...
http://emptyhammock.com/
http://edjective.org/
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] FindOpenSSL choosing unexpected OpenSSL install on Windows
Short form: I tell FindOpenSSL where to look by setting OPENSSL_ROOT_DIR to
point to my shiny new OpenSSL install; it ignores me and finds ancient,
vulnerable OpenSSL libraries to use instead.)
Some info about my build environment:
* pristine install of cmake 2.8.12.2-win32-x86
* "Open VS2012 x64 Native Tools Command Prompt"
* previously installed OpenSSL 1.0.1e via Win64 installer from
http://slproweb.com/products/Win32OpenSSL.html; installed to
%HOME%\OpenSSL-Win64, and apparently in registry
* trying to use my own OpenSSL build in %HOME%/PREFIXES/251 (lib, bin,
include, etc.), built in a "normal" manner: "perl Configure no-asm
--prefix=XXX VC-WIN64A" followed by "ms\do_win64a.bat"
With the following cmake invocation for Apache HTTP Server, libraries from
the old binary install of OpenSSL are being used instead of my new build:
mkdir C:\Users\Trawick\BUILDDIRS\251\httpd
cd C:\Users\Trawick\BUILDDIRS\251\httpd && cmake
-DCMAKE_INSTALL_PREFIX=C:\Users
\Trawick\PREFIXES\251 -G "NMake Makefiles"
-DCMAKE_BUILD_TYPE=RelWithDebInfo -DO
PENSSL_ROOT_DIR=C:\Users\Trawick\PREFIXES\251 -DENABLE_MODULES=a
-DINSTALL_MANUA
L=OFF C:\Users\Trawick/svn/httpd
-- The C compiler identification is MSVC 17.0.61030.0
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio
11.0/VC/bin/amd64/cl.exe
-- Check for working C compiler: C:/Program Files (x86)/Microsoft Visual
Studio
11.0/VC/bin/amd64/cl.exe -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Found LibXml2: C:/Users/Trawick/PREFIXES/251/lib/libxml2.lib (found
version "
2.9.1")
-- Found Lua51: C:/Users/Trawick/PREFIXES/251/lib/lua5.1.lib (found version
"5.1
.5")
-- Found OpenSSL:
optimized;C:/Users/Trawick/OpenSSL-Win64/lib/VC/ssleay32MD.lib
;debug;C:/Users/Trawick/OpenSSL-Win64/lib/VC/ssleay32MDd.lib;optimized;C:/Users/
Trawick/OpenSSL-Win64/lib/VC/libeay32MD.lib;debug;C:/Users/Trawick/OpenSSL-Win64
/lib/VC/libeay32MDd.lib (found version "1.0.2")
...
Interestingly, the version of the old binary install of OpenSSL is 1.0.1e,
whereas the version of my build is 1.0.2 (pre-release). FindOpenSSL thinks
it has 1.0.2 but points to the old libraries.
To filter out the obvious suggestion of uninstalling the old binary, I'm
trying to document how to make this work as expected for an arbitrary set
of users of Apache HTTP Server (httpd) on Windows, who might just need to
quickly build a new OpenSSL version and be sure that it is used, regardless
of what they or some product install may have done months or years earlier.
("Heartbleed" anyone?) Here is my current warning to users, should they
read it:
http://svn.apache.org/viewvc/httpd/httpd/trunk/README.cmake?r1=1541922&r2=1583027&diff_format=h
(But I think the real problem is the registry entry created by the old
binary install, not the "well-known" location.)
The httpd cmake list would not seem to be at fault here (see
http://svn.apache.org/viewvc/httpd/httpd/trunk/CMakeLists.txt?view=markup),
though I'd be thrilled if it was and could fix it.
The issue is clearly related to FindOpenSSL's preference for libraries with
"MD", "MDd", "MT", "MTd", or other such suffixes, which are not created by
a normal OpenSSL build. Somehow it is willing to bypass OPENSSL_ROOT_DIR
to find them.
It isn't clear to me why FindOpenSSL would care about the binary build if
OPENSSL_ROOT_DIR has been set:
if (WIN32)
# http://www.slproweb.com/products/Win32OpenSSL.html
set(_OPENSSL_ROOT_HINTS
${OPENSSL_ROOT_DIR}
"[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\OpenSSL
(32-bit)_is1;Inno Setup: App Path]"
"[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\OpenSSL
(64-bit)_is1;Inno Setup: App Path]"
ENV OPENSSL_ROOT_DIR
)
(and still other locations in the search path, most of which seem to be
possible locations where somebody installed one of those binary installers
from slproweb.com)
I don't think there's anything I can set on the cmake command-line to
circumvent this (any suggestions?).
I'd love to see a intuitive solution along the lines of setting a variable
respected by FindOpenSSL to the root install dir and it then ignores
everything else.
(Thanks to casey goodlett for walking me through FindOpenSSL after I
ambushed him at a user group meeting last night!)
Suggestions?
TIA!
--
Born in Roswell... married an alien...
http://emptyhammock.com/
http://edjective.org/
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link
Re: [CMake] CPACK_COMPONENT__DEPENDS doesn't work
What an honor for me that you guys responded so quickly. Our group has done well to move to CMake. Sorry for taking such a long time to reply; I'm part of a big organization that can be slow to decide things.
The way this is going, is to continue with one package rather than use a workaround, if we have some idea if/when CPACK_COMPONENT__DEPENDS will be implemented. But, am I understanding correctly that CPACK_COMPONENT__DEPENDS isn't expected to work? I see some CMake examples that use it so I'm confused why this works for some people.
I guess my question now is, is there a plan to make the CPACK_COMPONENT__DEPENDS mechanism work? At the risk of being asked to contribute :), is there any way to know when? My group can make a decision based on that info.
Thank you greatly!
Jeff
On Wed Nov 20 4:09 , Jeremy Fix sent:
On 11/20/2013 09:52 AM, Eric Noulard wrote:
> 2013/11/20 Jeremy Fix <jeremy@supelec.fr>:
>> Hello,
>>
>> I'm surprised CPACK_RPM_gui_PACKAGE_REQUIRES works , I don't find any use of
>> CPACK_RPM__REQUIRES in CPackRPM.cmake;
>
> Yes there is for all
>
> URL REQUIRES SUGGESTS PROVIDES OBSOLETES PREFIX CONFLICTS AUTOPROV
> AUTOREQ AUTOREQPROV
>
> see lines 555 and following we check for component specific value first:
>
> if(DEFINED CPACK_RPM_${CPACK_RPM_PACKAGE_COMPONENT}_PACKAGE_${_RPM_SPEC_HEADER})
>
> then
> else()
> if(DEFINED CPACK_RPM_PACKAGE_${_RPM_SPEC_HEADER})
>
> However we may have check the definition of
> "CPACK_COMPONENT__DEPENDS" first
> in order to fill-in CPACK_RPM__REQUIRES.
> This is not done.
>
> Moreover I'm not sure this could be easily factoired out since the
> syntax for dependency specification
> may well be package type specific (different name or syntax for DEB or
> RPM for example).
>
>> What I can suggest you for generating several packages with different
>> dependencies is to generate the different packages in multiple steps. If we
>> suppose you defined 2 components (in the INSTALL commands) called : binary
>> and devel ,you can then generate the packages (whether deb or rpm) as
>> follows:
>>
>>
>> SET(CPACK_INSTALL_CMAKE_PROJECTS "${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME};
>> ${MYBUILDTYPE};/")
>>
>> then for the dependencies:
>>
>> IF(MYBUILDTYPE STREQUAL "binary")
>> SET(CPACK_RPM_PACKAGE_REQUIRES "gsl")
>> SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libgsl0-dev")
>> ELSE()
>> SET(CPACK_RPM_PACKAGE_REQUIRES "gsl-devel")
>> SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libgsl0-dev")
>> ENDIF()
>>
>>
>> Then the packages are generated with:
>>
>> cmake -DMYBUILDTYPE="binary" && make package
>> cmake -DMYBUILDTYPE="devel" && make package
>
> You should be able to do that with component packaging and a
> CPACK_PROJECT_CONFIG_FILE.
>
I'm not familiar with CPACK_PROJECT_CONFIG_FILE;
I had issues with the package names generated with component packaging
as the component name is added at the end of the package name; I
prefered to generate the components in two steps to tweak the
CPACK_RPM_PACKAGE_NAME and I use some commands a bit more complicated
than the above;
IF(MYBUILDTYPE STREQUAL "binary")
SET(CPACK_RPM_PACKAGE_NAME ${CMAKE_PROJECT_NAME})
SET(CPACK_DEBIAN_PACKAGE_NAME ${CMAKE_PROJECT_NAME})
SET(CPACK_PACKAGE_FILE_NAME
${CMAKE_PROJECT_NAME}-${PACKAGE_VERSION}-${CMAKE_SYSTEM_PROCESSOR})
SET(CPACK_INSTALL_CMAKE_PROJECTS
"${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME};binary;/")
ELSEIF(MYBUILDTYPE STREQUAL "devel")
SET(CPACK_RPM_PACKAGE_NAME ${CMAKE_PROJECT_NAME}-devel)
SET(CPACK_DEBIAN_PACKAGE_NAME ${CMAKE_PROJECT_NAME}-devel)
SET(CPACK_PACKAGE_FILE_NAME
${CMAKE_PROJECT_NAME}-devel-${PACKAGE_VERSION}-${CMAKE_SYSTEM_PROCESSOR})
SET(CPACK_INSTALL_CMAKE_PROJECTS
"${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME}-devel;devel;/")
ENDIF()
This is just to ensure consistency between the field "Name:" in the
autogenerated spec file is :pkg and pkg-devel ;
and the generated RPM (or deb) filenames: pkg-1.00-i686.rpm and
pkg-devel-1.00-i686.rpm
jeremy.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitwar
[CMake] CPACK_COMPONENT__DEPENDS doesn't work
Hello CMake group, I'm trying to do a component-based install that will produce multiple packages, where one package depends on another. I am using cmake version 2.8.12.1. Have multiple packages working well but the dependencies have not been easy. The variable CPACK_COMPONENT__DEPENDS, given by the command `cpack --help-variable-list`, as far as I can tell, does nothing. Surprisingly, what ended up doing the trick on an RPM-based system is: SET(CPACK_RPM_gui_PACKAGE_REQUIRES "my-lib >= 0.1.1") Why does this work? This is inconsistent with the documentation. The bigger problem, I'm trying to solve at the moment, is how to make component dependencies work on Debian. I have tried every combination of cpack variable + component name and nothing stops an install with a message like, "Unable to install gui because it depends on my-lib" (because my-lib doesn't exist so it should halt the installer). Does component-based install even work for Debian (actually, I'm on ubuntu but whatever)? I saw about two references to it on the entire Internet so a good resource is hard to find, currently. It would be idea if I can use CPACK_COMPONENT__DEPENDS for both deb and rpm but as I said, it doesn't work. Thank you for any help/guidance. Jeff -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] problems when upgrading to Xcode v5
Hello,
I recently upgraded to Xcode v5 on Mac OSX and started getting build failures.
Below is a simplified project that produces the same problem, followed by the
error message generated by Xcode. The problem occurs with version v5 but not
v4.6.x of Xcode. I'm running CMake 2.8.10.2.
CMakeLists.txt
cmake_minimum_required ( VERSION 2.8.8 )
project( test )
add_library( a_obj OBJECT t1.c t2.c )
add_library( b_obj OBJECT t3.c t4.c )
add_library( a dummy.c $ )
add_library( b dummy.c $ )
add_executable( t t.c )
target_link_libraries( t a b )
::
t.c
::
#include
int func1( int a );
int func2( int a );
int func3( int a );
int func4( int a );
int main()
{
int a = 100;
printf( "%d %d %d %d %d\n", a, func1(a), func2(a), func3(a), func4(a) );
return 0;
}
::
t1.c
::
int func1( int a )
{
return a*1;
}
::
t2.c
::
int func2( int a )
{
return a*2;
}
::
t3.c
::
int func3( int a )
{
return a*3;
}
::
t4.c
::
int func4( int a )
{
return a*4;
}
dummy.c is empty
When I run CMake, no errors; running xcodebuild gives:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool:
can't open file:
/Users/jschenck/TestBuild/test.build/Release/a_obj.build/Objects-normal/undefined_arch/t1.o
(No such file or directory)
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool:
can't open file:
/Users/jschenck/TestBuild/test.build/Release/a_obj.build/Objects-normal/undefined_arch/t2.o
(No such file or directory)
Command
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool
failed with exit code 1
The .o files can instead be found here:
$ find . -name t1.o
./test.build/Release/a_obj.build/Objects-normal/x86_64/t1.o
Thanks for your help. (Sorry for not running this on the latest version of
CMake, but I rolled back Xcode to an earlier version and now will have a hard
time reproducing it. If necessary, I can "upgrade" again.)
Regards,
Jeff Schenck
Notice:
This message and any included attachments are intended only for the use of the
addressee, and may contain information that is privileged or confidential. If
you are not the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please destroy
the original message and any copies or printouts hereof.
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
[CMake] FindOpenSSL always uses system libs
If you have a (linux or solaris) system with openssl installed in /usr and a second copy installed elsewhere (e.g., /opt) and you want a cmake project to find the elsewhere version, no matter what you try it finds the system copy. (In other words, OPENSSL_ROOT_DIR has no effect.) Are we missing something or is this a bug in FindOpenSSL? We've tested cmake 2.8.5, 2.8.8, and 2.8.11 without any luck. Thanks, Jeff. Example: jsipek@poseidon:/tmp/ssltest$ cat CMakeLists.txt cmake_minimum_required(VERSION 2.8.5) project(test) find_package(OpenSSL REQUIRED) jsipek@poseidon:/tmp/ssltest$ rm CMakeCache.txt && OPENSSL_ROOT_DIR=/tmp/ossl/ cmake . -DOPENSSL_ROOT_DIR=/tmp/ossl/ -- The C compiler identification is GNU 4.6.3 -- The CXX compiler identification is GNU 4.6.3 -- Check for working C compiler: /usr/gnu/bin/gcc -- Check for working C compiler: /usr/gnu/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/gnu/bin/c++ -- Check for working CXX compiler: /usr/gnu/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found OpenSSL: /usr/lib/libssl.so;/usr/lib/libcrypto.so (found version "0.9.8x") -- Configuring done -- Generating done -- Build files have been written to: /tmp/ssltest jsipek@poseidon:/tmp/ssltest$ find /tmp/ossl/lib/ /tmp/ossl/lib/ /tmp/ossl/lib/engines /tmp/ossl/lib/pkgconfig /tmp/ossl/lib/pkgconfig/libcrypto.pc /tmp/ossl/lib/pkgconfig/libssl.pc /tmp/ossl/lib/pkgconfig/openssl.pc /tmp/ossl/lib/libcrypto.a /tmp/ossl/lib/libssl.a -- mainframe, n.: An obsolete device still used by thousands of obsolete companies serving billions of obsolete customers and making huge obsolete profits for their obsolete shareholders. And this year's run twice as fast as last year's. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
[CMake] Cross compile an external makefile project.
I have a project to port to the raspberry pi.
I managed to get boost to cross-compile with the externalproject_Add on windows
and am trying to do something similar with curl.
Because curl uses make and not bjam, I switched over to a linux build agent but
I am having difficulty.
Everything seems good at the beginning, it detects my compiler and the linux
build but then before the un-tar stage it says changes have been made that
require restarting cmake and it then fails to detect the compiler and stops.
Cmake is 2.8.7 on Ubuntu build image.
Is there an example of combining cross-compiling with an externalProject_add.
{There are a lot of options for a trial and error technique, I am getting tired
of guessing :)}
BTW. Does it set and pass CC variables and prefixes that are in the cmake
settings or do I have to manually pass them like I did with bjam.
Thanks.
Jeff Shanab, Manager-Software Engineering
D 630.633.4515 | C 630.453.7764 | F 630.633.4815 |
jsha...@smartwire.com<mailto:jsha...@smartwire.com>
[MVSSig]
This message and any attachments contain confidential and proprietary
information, and may contain privileged information, belonging to one or more
affiliates of Windy City Wire Cable & Technology Products, LLC. No privilege is
waived by this transmission. Unauthorized use, copying or disclosure of such
information is prohibited and may be unlawful. If you receive this message in
error, please delete it from your system, destroy any printouts or copies of
it, and notify the sender immediately by e-mail or phone.
<>--
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] Compile error- select() support
I have an old sparc system running Linux on which I am trying to compile CMake. I am able to bootstrap just fine, but when I run make, I get the following error: Building C object Utilities/cmcurl/CMakeFiles/cmcurl.dir/select.o ~/cmake-2.8.4/Utilities/cmcurl/select.c:39:2: error: #error "We can't compile without select() support!" I have been unable to find any direction on the Internet. Is the select function something I can compile and install? Is it a limitation of my hardware? Is there a workaround if I am unable to get select() support? Thank you in advance. Jeff Dahl ___ 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 + VS Toolkit 2003
Benoit; I too am using cmake on a 64-bit box, albeit linux, not windows. IN any event, we had no end of troubles using the 64-bit version of cmake, we even rebuilt it, no joy. We stuck with the 32-bit version and have had no real problems since. I doubt this helps you much but it got us going. Cheers, Jeff Benoit Regrain wrote: Hi, I would generate the compilation files for the VisualStudio Toolkit 2003 with CMake, but it doesn't work. I have followed the instructions at www.itk.org/Wiki/ITK_MS_Free_Tool but CMake says that it can't compile for IA64... How could I solve my problem ? - Benoit Regrain Ingénieur d'études CNRS (Creatis) email : [EMAIL PROTECTED] phone : (+33) (0) 4.72.43.82.58 fax : (+33) (0) 4.72.43.85.26 address : CREATIS - CNRS UMR5515 INSA - Bâtiment Blaise Pascal 7, avenue Jean Capelle F - 69621 Villeurbanne Cedex - ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
