From: Robert Maynard [robert.mayn...@kitware.com]
Sent: Tuesday, December 18, 2018 11:08 AM
To: Daniel Schepler
Cc: CMake MailingList
Subject: Re: [CMake] How to link in different prebuilt objects based on
configuration
As far as I know this is a limitation of the MSVC project files
ot;:
E:/EXata_7_0/qualnet_dev_13_Dec18/kernel/obj/exata-main-windows-x64-vc14.obj
---
(This object file is marked with source file property EXTERNAL_OBJECT=1.)
Is this a limitation in Visual Studio projects, or a limitation in CMake? In
either case, what workaround could allow this build to sup
Personally, I find it much simpler just to expect the Path to include the
locations of the DLL files as opposed to copying them. (And I often write
small batch scripts to set up this development environment, and then optionally
start cmake-gui.exe / devenv.exe / etc.)
--
Daniel Schepler
nstaller and the NSS modules from the system.
For the latter, the OpenGL libraries vary too much between Mesa and the NVidia
and AMD proprietary driver versions for any one of them to work on all systems.)
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org
Another alternative, which is the one we use here, is to configure the custom
Qt build with a "-qtlibinfix" flag - which produces libraries with completely
different SONAMEs so there's no conflict. (We use this in conjunction with an
RPATH.) One thing that could break is that some
sitory). So overall, it's been
a big improvement over what we used to do, which was to try to maintain binary
builds of the third-party libraries in SVN.
--
Daniel Schepler
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake
Makefiles" generator, then the compiler would give
a warning on each source file because the build system was passing both the
default /MD[d] and the additional /MT.
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Walter Gray
[chrysal...@gmail
I don't see this in a quick scan through
CMAKE_DIR/share/cmake-3.5/Help/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.rst. This
would be the C++11 addition under
http://en.cppreference.com/w/cpp/language/storage_duration#Static_local_variables
- or, the feature matrix at
would be totally non-portable to
Windows.
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Dmitry Marakasov
[amd...@amdmi3.ru]
Sent: Sunday, November 29, 2015 6:10 PM
To: cmake@cmake.org
Subject: [CMake] Best way to handle application data p
I'm assuming this is under a Unix platform - in my experience, on Windows, I
get the color escape codes even running cmake builds under Jenkins. On Unix
platforms, you could install expect and use the unbuffer tool, e.g. "unbuffer
make -j8 -k".
--
Danie
Doesn't CMAKE_PREFIX_PATH work for you?
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Michael Jackson
[mike.jack...@bluequartz.net]
Sent: Friday, September 04, 2015 10:33 AM
To: CMake list
Subject: Re: [CMake] Protobuf Libraries not found
This seems to work for me:
set(CMAKE_BUILD_TYPE_INIT RelWithDebInfo)
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Dan Kegel [d...@kegel.com]
Sent: Friday, July 31, 2015 9:38 AM
To: Ruslan Baratov
Cc: cmake; Bill Hoffman
Subject: Re
CMAKE_USER_MAKE_RULES_OVERRIDE so they can be dependent on detected
platform/compiler settings).
--
Daniel Schepler
From: daniel.r.ke...@gmail.com [daniel.r.ke...@gmail.com] on behalf of Dan
Kegel [d...@kegel.com]
Sent: Friday, July 31, 2015 10:21 AM
)?
--
Daniel Schepler
--
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
...@gmail.com]
Sent: Wednesday, April 29, 2015 4:46 PM
To: Daniel Schepler
Cc: cmake@cmake.org
Subject: Re: [CMake] Linking to MySQL C++ Connector libraries using extra
flags, Ubuntu 14.04 LTS, gcc
Hello Daniel,
Thanks for your help.
I took your file and plagiarized it, replacing
MariaDB/MARIADB/mariadb
})
target_link_libraries(mainexe ${MARIADB_LIBRARY})
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Peleg Bar-Sapir
[pel...@gmail.com]
Sent: Wednesday, April 29, 2015 2:56 PM
To: cmake@cmake.org
Subject: [CMake] Linking to MySQL C++ Connector libraries
on the first
CMake run.
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Daniel Schepler
[dschep...@scalable-networks.com]
Sent: Wednesday, April 29, 2015 11:20 AM
To: cmake@cmake.org
Subject: [CMake] Issues with adding -flto in CMAKE_C[XX
- target_link_libraries(entity_find_visual
${OpenCV_LIBS} ${MYSQL_LIBRARY}).)
--
Daniel
From: Peleg Bar-Sapir [pel...@gmail.com]
Sent: Wednesday, April 29, 2015 5:29 PM
To: Daniel Schepler
Cc: cmake@cmake.org
Subject: Re: [CMake] Linking to MySQL C
As I understand it, configuration-specific properties are deprecated in favor
of generator expressions. For example:
target_compile_options(openjpeg PRIVATE
$$CONFIG:Release:-ffast-math)
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org
Would this work?
target_compile_options(core.x PUBLIC ${MPI_C_COMPILE_FLAGS})
--
Daniel
From: CMake [cmake-boun...@cmake.org] on behalf of Alexander Droste
[alexander.ra.dro...@googlemail.com]
Sent: Friday, April 03, 2015 2:54 PM
To: Thompson, KT
Cc:
Droste [alexander.ra.dro...@googlemail.com]
Sent: Friday, April 03, 2015 3:19 PM
To: Daniel Schepler
Cc: cmake@cmake.org
Subject: Re: [CMake] how to use the FindMPI module correctly?
Do you mean just using:
target_compile_options(core.x PUBLIC ${MPI_C_COMPILE_FLAGS})
but not:
include_directories
Here, to generate XML for Jenkins' xUnit plugin, we run ctest -T Test -j2
which has never complained about missing DartConfiguration.tcl.
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Robert Dailey
[rcdailey.li...@gmail.com]
Sent
subdirectory for building projectlib sources - which is probably what you want
in order to be able to resolve inter-header dependencies.)
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of Chris Johnson
[cxjohn...@gmail.com]
Sent: Monday
(INSTALL \${libfile_target} DESTINATION
\$ENV{DESTDIR}\${CMAKE_INSTALL_PREFIX}/gui/lib/${BUILD_PLATFORM_BASE})
endif ()
endif ()
endforeach ()
COMPONENT gui)
endif ()
--
Daniel Schepler
-Original Message-
From: CMake
This should hopefully be an easy question: Our build of FreeImage has a
dependency on vcomp120.dll. However, it would seem that GetPrerequisites.cmake
is skipping that dependency because it's in the Visual Studio installation
directory, and also InstallRequiredSystemLibraries.cmake doesn't
Why would we need specific support for each compiler? Couldn't the module use
check_cxx_source_compiles() etc. tests instead?
--
Daniel Schepler
From: CMake [cmake-boun...@cmake.org] on behalf of NoRulez [noru...@me.com]
Sent: Monday, December 15, 2014 5
And what if there are more dependencies? For example, we have a project here
that uses Qt, Boost, OGRE, MYGUI, GDAL, Protobuf and EXPAT at least. And then
if some of those builds aren't self-contained, you could add in dependencies
like OpenSSL, libjpeg, libpng, etc. It seems like all those
: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Bill Somerville
Sent: Friday, October 31, 2014 2:12 PM
To: cmake@cmake.org
Subject: Re: [CMake] Copying DLLs to output directory
On 31/10/2014 20:46, Daniel Schepler wrote:
And what if there are more dependencies? For example, we have a project
Where would I find the list of available C++ language features? For instance,
I would suppose there's one for auto, one for move constructors/assignment
operators, and one for = delete of default constructors/destructors et al.
These are probably the ones we'd be most interested in here, for
, October 29, 2014 10:43 AM
To: Daniel Schepler
Cc: CMake MailingList
Subject: Re: [CMake] [ANNOUNCE] CMake 3.1.0-rc1 now ready for testing!
You can find the known compile features that can be detected at:
http://www.cmake.org/cmake/help/v3.1/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.html
At the end
Thanks for the pointers, that does answer my question. I would just set
CXX_STANDARD to 11 and leave CXX_STANDARD_REQUIRED unset.
--
Daniel
From: David Cole [mailto:dlrd...@aol.com]
Sent: Wednesday, October 29, 2014 11:38 AM
To: Daniel Schepler
Cc: cmake@cmake.org
Subject: Re: [CMake] [ANNOUNCE
I think this should work:
$$NOT:$CONFIG:Debug:${my_release_libs}
--
Daniel
-Original Message-
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Robert Dailey
Sent: Monday, October 27, 2014 5:12 PM
To: CMake
Subject: Re: [CMake] Refer to all debug or release targets with
What about checking install_manifest.txt after running the cmake command?
Or, if you have multiple components to package in this way, possibly you could
use a different CMAKE_INSTALL_PREFIX for each component. Then, either have the
installer generator use those directories for packing the
resolves the issue.
--
Daniel Schepler
--
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
Maybe you need to set it to C:/software/propgcc/bin/propeller-elf-gcc.exe
instead? (Or ${WHATEVER_PATH}/propeller-elf-gcc${CMAKE_EXECUTABLE_SUFFIX} .)
--
Daniel
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of da...@zemon.name
Sent: Wednesday, August 06, 2014 8:50 AM
To:
will put non-system
libraries into a self-contained bundle so we'll still want $ORIGIN as the RPATH
there.) I haven't found any setting that will do this by scanning the
rpath-related CMake variables or target properties.
--
Daniel Schepler
--
Powered by www.kitware.com
Please keep messages
36 matches
Mail list logo
