t;
> If all the SWIG wrappers load the libraries dynamically (which glancing at
> the examples it looks like they do), MODULE is more fitting. However since I
> can’t find much on what platforms actually support this I don’t see the
> point in using it over SHARED.
>
> -Caleb
nd only include
> the code needed for the lib’s interface. A static lib potentially leaks a
> lot more about your build/files/etc instead of shared libs. Shared libs are
> generally smaller too.
>
> -Caleb
>
> On Sat, Dec 9, 2017 at 1:00 PM Rob McDonald
> wrote:
>>
In version 3.8, SWIG_ADD_MODULE was deprecated in favor of
SWIG_ADD_LIBRARY. This added the ability to control the TYPE for the
target. From the documentation, the options are this:
https://cmake.org/cmake/help/v3.8/module/UseSWIG.html
TYPE
However, I can find no documentation of what these o
CMAKE_POSITION_INDEPENDENT_CODE first appears in the documentation for
2.8.9 while CMAKE_POSITION_INDEPENDENT_FLAGS appears in the docs for
2.8.8 -- with the same description.
Was this just a documentation typo, or did the name of this variable
change from 2.8.8 to 2.8.9? Only the _FLAGS version
Is there a continuation of the CMake version -- feature mapping table?
https://cmake.org/Wiki/CMake_Version_Compatibility_Matrix
I found this to be quite useful, but need something that continues into 3.X.
Rob
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
On Ubuntu 14.04 (CMake 2.8.12.2), FindFLTK.cmake sets
FLTK_FLUID_EXECUTABLE to '/usr/bin/fluid'. This is good.
On 15.10 (CMake 3.2.2), FLTK_FLUID_EXECUTABLE gets set to 'fluid'. This is bad.
An eyeball comparison of the FindFLTK.cmake scripts included with each
doesn't reveal anything suspiciou
All,
I have a SuperProject set up with ExternalProject_add the way some
other projects do.
The SuperProject has two EP's -- Libraries and Main. Libraries has a
bunch of its own EP's. Main is my core project.
When some users use this setup, they're confused at the end --
everything has worked,
On a Mac, using GCC's global -static is bad, so that doesn't work out.
However, as it turns out, -static-libgcc implies all parts of libgcc,
including libgomp. So, building with -static-libgcc -static-libstdc++
looks like the best solution.
Rob
On Thu, Apr 30, 2015 at 2:19 PM, Ro
I'm using MacPorts GCC 4.8 and CMake 3.2.
I use 'FIND_PACKAGE( OpenMP )', and then use OpenMP_C_FLAGS and
OpenMP_CXX_FLAGS appropriately.
My application works on the machine that I build on. However, users
without MacPorts GCC installed can't find libgomp.1.dylib on their
machine.
I'd like to t
I've used ExternalProject_Add to trick CMake into supporting two
compilers to build my project.
Part of my project needs OpenMP, but other parts do not. So, on
MacOS, I would prefer to build most of the project with CLang, but the
OpenMP requiring part with gcc.
I have CMake set up to detect whe
Sorry for the noise. My Cache had variables leftover from VS 2010 Express.
Thanks,
Rob
On Wed, Apr 8, 2015 at 3:44 PM, Rob McDonald wrote:
> For some reason, FindOpenMP succeeds -- but reports failure for me on
> Visual Studio 2010 Pro. This is with the latest CMake just in case...
For some reason, FindOpenMP succeeds -- but reports failure for me on
Visual Studio 2010 Pro. This is with the latest CMake just in case...
1> -- Try OpenMP C flag = [/openmp]
1> -- Performing Test OpenMP_FLAG_DETECTED
1> -- Performing Test OpenMP_FLAG_DETECTED - Success
1> -- Try OpenMP CXX
Ok, I think I've answered my own question...
I added the following after the ExternalProject_Add command...
ExternalProject_Get_Property( ALTBUILD BINARY_DIR )
INSTALL( PROGRAMS ${BINARY_DIR}/myprogram DESTINATION . )
Rob
On Sat, Apr 4, 2015 at 12:57 PM, Rob McDonald wrote:
> All,
&g
All,
I have a project that is typically compiled with CLang/LLVM. However,
I'm now adding a component that is preferentially built with OpenMP.
CLang doesn't support OpenMP, so I'd like to build that component with
GCC while still building everything else with CLang.
So far, I'm approaching the
I am familiar with UseLATEX, but would like to take the automation of
my document build system a step or two further. Solutions that build
on UseLATEX -- or a totally separate approach, are OK.
I often use Matlab to create *.pdf figures -- which are then used in a
LaTeX document. I would like my
97c84d1ebda89cce3b4/SuperBuild/External_teem.cmake#L13-16
>
> Hth
> Jc
>
>
> On Thu, Feb 13, 2014 at 12:51 PM, Rob McDonald
> wrote:
>
>> When I search for a given library, specifying multiple possible names and
>> multiple hints for paths...
>>
>> FIND
When I search for a given library, specifying multiple possible names and
multiple hints for paths...
FIND_LIBRARY( FINDME_LIB
NAMES name1 name2 name3
HINTS path1 path2 path3
DOC "Library to find")
CMake seems to have a preference for name1, and it first searches all HINTS
All,
I'm building FLTK as an ExternalProject to a 'Libraries' project. Inside
the ExternalProject, I'm using the FLTK CMake build system.
I've then created a SuperProject to build Libraries as an ExternalProject
(and my main project too). This works great so far on my Mac.
On my Windows machin
Is there a way to get cmake to report back an _actual_ minimum required
version?
Our project has lots of parts, and the CMakeLists.txt have not been very
well maintained. Right now, CMAKE_MINIMUM_REQUIRED is set to different
values throughout, none of which are likely correct.
It seems like it '
Thanks to everyone for all the helpful responses. It looks like most of
the ideas were pretty similar to what I was thinking. Glad to know I
wasn't missing anything huge.
I had found UniversalIndentGUI and plan on using it. I had also found
uncrustify and will take a closer look at it.
On Fri
All,
I'm interested in adding a code beautifier to my project. I'm looking at
AStyle, but am open to others.
Implementing a FindAStyle.cmake is pretty trivial. Likewise, implementing
custom targets is pretty straightforward in the simple case.
However, I thought there might be some canonical/i
I feel like this is a really dumb question, but I've got myself wrapped
around the axel
I'd like to use a negative conditional on a variable that may or may not be
defined... say USE_SYSTEM_FOO
So, I'd like to do something like this...
IF( NOT ${USE_SYSTEM_FOO} )
# Build my own FOO
ENDI
On Mon, Jan 20, 2014 at 7:39 AM, J Decker wrote:
> On Mon, Jan 20, 2014 at 7:37 AM, Игорь Пашев
> wrote:
> > 2014/1/20 Rob McDonald :
> >> We also have an API/Library mode with no main(), but that can have
> graphics
> >> or not.
> >
> > So, one wil
My project can be compiled with support for graphics, or in a completely
headless mode with no dependencies on any graphics libraries. By and
large, this is accomplished with the same source code and a very few
#define 's.
We also have an API/Library mode with no main(), but that can have graphic
>
> On Sun, Jan 12, 2014 at 1:39 AM, Rob McDonald wrote:
>
>> Where does CMake get its patch implementation?
>>
>
> It doesn't. It would be great if CMake implemented a "cmake -E patch".
>
Agreed.
>
> Problem is patch from GNUWin32 does not sup
Where does CMake get its patch implementation?
I'm using a patch step with ExternalProject_Add on Windows (and other
platforms).
I had it working on one Windows machine - which unfortunately just got
knocked off a desk and will never be recovered. The same files on a
different Windows machine do
All,
My FLTK EmbeddedProject woes are solved. As it turns out, the path of
least resistance was the one I hadn't tried
While the FLKT CMake files were indeed out of date, they weren't that bad.
Fixing them was by far the best solution.
I have a few more libraries for my project, but hopefu
s
or nmake files. All the common examples drive either ./configure, pure
make, or CMake setups.
Rob
On Thu, Jan 9, 2014 at 11:28 AM, Bill Hoffman wrote:
> On 1/9/2014 2:13 PM, Rob McDonald wrote:
>
>> Bill,
>>
>> This sounds interesting. After FLTK, I have a couple
to support 32/64 target,
but you can't set target without knowing the host environment. Is there a
CMake way to detect whether the Visual Studio host environment is 32/64 bit?
On Thu, Jan 9, 2014 at 10:48 AM, Rob McDonald
wrote:
>
> Correct, this is one of the concerns that makes i
Correct, this is one of the concerns that makes it more complex than just
searching for the first vcvarsall.bat you come to.
I'd like to match up the vcvarsall to the version of visual studio
currently in use by CMake.
I think there are now enough pieces that I can write a CMake
'FindVSEnvironmen
s.
I tried something like the following
BUILD_COMMAND
${CMAKE_COMMAND} --build -- gmake
But, it didn't seem to do anything useful
Rob
On Wed, Jan 8, 2014 at 5:31 PM, J Decker wrote:
> cmake --build
>
> On Wed, Jan 8, 2014 at 3:53 PM, Rob McDonald
> wrote:
>
s I know, I never run msbuild.
The command line Makefile driven system Erco put together (the non-FLTK
download link from before) is a one-stop shop.
By running 'gmake.bat', it configures the program and then launches the
build via gmake.exe. I do not believe it ever creates a *.prj o
Short version:
Does anyone have an elegant way to launch the visual studio command line
from within CMake?
James Bigler asked essentially this question back in March of 2011. David
responded with a link to a Blog entry, but I haven't figured out how to
translate that into something that works.
All,
Thanks for all your work on CMake. I really hate toolchain problems and
CMake makes them almost bearable. The entire community of developers
trying to make cross platform programs would be far worse off without CMake.
My project is a big open source C++ project with lots of library
depende
34 matches
Mail list logo