[CMake] Mac Xcode 11 Generator bug/problem with CODE_SIGN_IDENTITY default

I hit a problem with the CMake/Xcode Generator using Xcode 11. (I think this problem started in Xcode 10 actually, but now I'm blocked really hard and need to solve this.) By default, Xcode is now trying to do "Sign to run locally" for the Code Signing Identity (CODE_SIGN_IDENTITY) property, by

Re: [CMake] CMake on Raspberry Pi

On 5/20/18, Shawn G wrote: > Hi there, im having some troubles installing CMake on raspberry pi 3 > running raspbian stretch. > I keep getting this error message when i run the command "sudo apt-get > install build-essential cmake pkg-config" > The error message: > " Reading

Re: [CMake] How to build CMake so it works on an older Linux?

On 4/5/18, Robert Maynard wrote: > The official CMake binaries do the same thing as you and build with a > static libstdc++ and libgcc. > As far as dependencies we use static builds of those too, with most > being the version provided inside CMake, and an external

Re: [CMake] How to build CMake so it works on an older Linux?

Thanks for the responses. Yes, I just need this to run on Ubuntu 12.04 (and some other old Linux's in that era). Yes, I think the probably is the libstdc++ dependency. As pointed out, it is really hard to get a newer compiler on Ubuntu 12.04. I've been down this road before, and if memory serves,

[CMake] How to build CMake so it works on an older Linux?

I just discovered that CMake no longer builds on my Ubuntu 12.04. I need to build binaries that are compatible with that ABI. I see that your binary distribution of CMake 3.11 still works on Ubuntu 12.04. Can you tell me what you do to achieve this? What are you doing for your official builds?

[CMake] Swift Makefile/Ninja generator: trying to bring up to date

Hi, I know it’s been awhile since I last posted anything about this. Since my last post, I had quietly added to the Ninja backend to bring it to par with the initial work I did on the Makefile generator. This was partly done because I was trying to get compatibility with Android which uses the

Re: [cmake-developers] Future of ccmake and cmake-gui and internationalization

> If small and self-reliant are the criteria, how does FLTK > (http://www.fltk.org/index.php) stack up? For something like > cmake-gui it would probably work just fine, and AFAIK it doesn't > require GTK... it uses LGPLv2 with a static linking exception, so > it's probably as good/better than

Re: [cmake-developers] Future of ccmake and cmake-gui and internationalization

I hope I'm doing this right...but the resulting program I think looks correct testing on my Mac. Attached are two pictures. The first is a simple label in a window. The second is from your MessageBox line. Thanks, Eric -- Powered by www.kitware.com Please keep messages on-topic and check the

Re: [cmake-developers] Future of ccmake and cmake-gui and internationalization

> Hi Eric: > > My opinion is your point about size is weak because IUP normally depends on > a big suite of graphical libraries in the GTK+ case or a big set of > system libraries such as GDI/GDI+/Uniscribe or Direct2D/DirectWrite in > the Windows case. > On systems the provide first class native

Re: [cmake-developers] Future of ccmake and cmake-gui

> How easy is it to ship binaries which work on any platform without also > shipping all of the necessary platform backends as well? So on Windows and Mac, there is only one backend, the native one. And so there is nothing to manage. On the remaining Unix's with IUP you pick one when you build

Re: [cmake-developers] Future of ccmake and cmake-gui

On 8/16/17, Jean-Michaël Celerier <jeanmichael.celer...@gmail.com> wrote: > @Eric Wing >> I am not making a strong push for this, but I want to bring it up to > at least get people thinking about this... I am disturbed by the size > and complexity of Qt. My past experienc

Re: [cmake-developers] Future of ccmake and cmake-gui

On 8/15/17, Daniel Pfeifer wrote: > Hi, > > With !977 merged, it is possible to base ccmake and cmake-gui on top of the > cmake server. > For demonstration, I copied the contents of the Source/CursesDialog > directory and added a proxy implementation of the classes `cmake`

Re: [cmake-developers] iOS: direction to official support and questions

I've been using a derivative of the iOS toolchain for many years that you probably can find easily with a Google search. It has a lot of shortcomings, but it generally works. And most of the shortcomings I think are only solvable by properly fixing/modifying the CMake core. On 8/15/17, Raffi

Re: [CMake] CMake + Gradle for Android

On 8/8/17, Jom O'Fisher wrote: > Yeah, we'd like to support any CMake more recent than 3.7.0 (which is the > first version to support server mode). So your fork would need to be based > on a somewhat recent CMake. We probably wouldn't support a path directly in >

Re: [CMake] CMake + Gradle for Android

Hi Jom, I'm glad to hear Android's CMake will eventually catch up. But since you are here, can you add a feature that allows a user to specify an alternate location for where CMake is located? There are two useful cases for this. 1) Users daring or desperate enough to try using a more recent

Re: [cmake-developers] Linking Apple frameworks

On 8/8/17, Brad King <brad.k...@kitware.com> wrote: > On 08/07/2017 05:27 PM, Eric Wing wrote: >> I think that would be a mistake because it seems that the only purpose >> of this change would be so you could bypass CMake and try to directly >> invoke some kind

Re: [cmake-developers] Linking Apple frameworks

On 8/7/17, Brad King wrote: > On 08/05/2017 07:58 PM, Craig Scott wrote: >> target_link_libraries(foo PRIVATE "-framework AppKit") >> >> Strangely, with the library quoted as above, the embedded space >> is not escaped, leading to the (desirable but surprising) result >

Re: [cmake-developers] Linking Apple frameworks

On 8/5/17, Craig Scott wrote: > I'm exploring the behaviour of target_link_libraries() where the library to > be linked is an Apple framework. As part of this, I noticed that the > following does not work: > > target_link_libraries(foo PRIVATE -framework AppKit) > > >

Re: [cmake-developers] [CMake] CMake integration in Gradle (Android Studio)

So I have been using (a custom) CMake + Android Studio/Gradle for some years now. I only recently saw that both official CMake is adding Android support, and that the official Android tools are supporting CMake. I’m actually still confused on the differences between the two and what each offers in

Re: [CMake] CMake integration in Gradle (Android Studio)

So I have been using (a custom) CMake + Android Studio/Gradle for some years now. I only recently saw that both official CMake is adding Android support, and that the official Android tools are supporting CMake. I’m actually still confused on the differences between the two and what each offers in

Re: [CMake] How to codesign .msi from WIX/CPack?

On 9/7/16, David Cole wrote: > There may be a hook at the CPack level you can implement, but I'd have to > dig to figure out what it is and if it even presently exists. > > The easy thing to do would be to implement a custom target which does two > custom commands: the first the

[CMake] How to codesign .msi from WIX/CPack?

I'm finally trying the WIX/CPack MSI generator. Pretty nice! One thing I need to do is instruct the build process to codesign via signtool.exe. I've managed to figure out how to codesign my .exe via a POST_BUILD add_custom_command step. But now I would like to make sure the .msi that gets

Re: [CMake] OSX Code Signing best practice

On 7/12/16, Harry Mallon wrote: > Hello all, > > What is the current best practice for code signing OSX .apps and binaries? I > am using: > > 1. MAC_OSX_BUNDLE for my .app targets. > 2. unix style executables > 3. dylibs > 4. A prefpane (which I haven't got working yet)

Re: [CMake] Mac OS X framework building

On 6/5/16, Bill Somerville wrote: > On 24/05/2016 21:55, Bill Somerville wrote: >> I am trying to make a framework using a shared library. The docs say >> that the target property PUBLIC_HEADER should be a list of interface >> header files that install(TARGET ...) will

Re: [cmake-developers] Problem with find_path and Frameworks

On 5/25/16, Harry Mallon wrote: > I have quite a specific problem with find_path where > "find_path(IOKIT_INCLUDE_DIR "IOKit/pci/IOPCIDevice.h")" returns > "/System/Library/Frameworks/Kernel.framework/Headers/IOKit/pci" rather than >

Re: [CMake] How to deal with generated source files (w/ dependency tracking) for globs

On 4/6/16, iosif neitzke wrote: > I think it depends on when you want the output files from Nim > generated and which files are the most frequently developed. > If it is usually a one-time generation per clean development session, > the simplest case, where the

Re: [CMake] How to deal with generated source files (w/ dependency tracking) for globs

On 4/4/16, Nicholas Braden wrote: > I haven't tested this myself, but instead of using a glob, you could > have a build step that generates a CMake script file with the list of > generated files in it (e.g. via execute_process to run another CMake > script whose only

[CMake] How to deal with generated source files (w/ dependency tracking) for globs

Hi, this is kind of a side problem that was asked of me. I'm not sure how many hoops I actually want to jump through to solve this. But, here's the situation. I have a really nice, traditional C based project in CMake. All my dependency tracking works really well for cross-platform and IDE

Re: [CMake] Best way to show/include CMake files in IDE

On 3/7/16, Eric Wing <ewmail...@gmail.com> wrote: > On 3/7/16, David Cole <dlrd...@aol.com> wrote: >> If you include those files in the source list for a library, executable, >> or >> custom target, they should show up in IDE projects, and they should be >>

Re: [CMake] Best way to show/include CMake files in IDE

On 3/7/16, David Cole wrote: > If you include those files in the source list for a library, executable, or > custom target, they should show up in IDE projects, and they should be > ignored by Makefile type projects. Have you tried that? > > > David > I haven't tried it yet

[CMake] Best way to show/include CMake files in IDE

I have a bunch of .cmake support files in my project that I have split off from CMakeLists.txt (using INCLUDE to combine them) to separate concerns. (Source files, application assets, script files, platform settings, codesigning, etc.) This works, but they don't show up in IDEs (Visual Studio,

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

I'm finding that I'm going to need to completely separate the C FLAGS from the Swift FLAGS. I hit some complicated situations where the C FLAGS (both compile and linker) are confusing the process and shouldn't be passed to Swift. I see in the CMakeSwiftInformation.cmake, there is a . However, I

Re: [cmake-developers] Support of Scala language

>> >>If we're starting with support for a new language then we should >>add it properly as a first-class language. Eric and Michael (in Cc) >>have been working on this for Swift and C# recently. Likely there >>is some overlap in design space. >> On 2/19/16, CHEVRIER, Marc

[CMake] Video glimpse of how I'm using CMake with Swift (and CMake in general)

I thought some of you might find this video I made interesting. It is a teaser video for a new 2D cross-platform game SDK I've been working on. It makes aggressive use of CMake for the build system. https://youtu.be/w8ftI9mpGdY The video goes by fast since is a time-lapse style. But hopefully

Re: [cmake-developers] Drop support for older Xcode versions?

On 2/9/16, Davy Durham wrote: > I'll say that in my line of work, we still have to support OS X 10.6 > (just dropped 10.5 support) .. And we're doing this at Apple's own > request/demand! It's not fun. I've had to hack tools around to get > somewhat newer tool chains to

Re: [cmake-developers] Drop support for older Xcode versions?

On 2/6/16, Gregor Jasny via cmake-developers wrote: > Hello, > > I'd like to get your feedback on deprecating or dropping support for > older Xcode versions. During changes on the Xcode generator it gets > harder and harder to test against old and very old Xcode

Re: [CMake] [cmake-developers] Drop support for older Xcode versions?

On 2/6/16, Gregor Jasny via cmake-developers wrote: > Hello, > > I'd like to get your feedback on deprecating or dropping support for > older Xcode versions. During changes on the Xcode generator it gets > harder and harder to test against old and very old Xcode

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 2/4/16, Brad King <brad.k...@kitware.com> wrote: > On 01/29/2016 03:16 PM, Eric Wing wrote: >> I need more guidance here. I'm not connecting the dots. >> My problem seems to be that the execute_process() in >> CMakeDetermineCompilerId.cmake is trying to invoke the co

Re: [cmake-developers] [ANNOUNCE] cmake-unit - A new unit testing framework for CMake

On 1/29/16, Brad King wrote: > On 01/25/2016 11:01 AM, Sam Spilsbury wrote: >> Over the last two years I've been working on a new unit testing >> framework for CMake. I started this project because I've been writing >> some other fairly complex CMake modules and I kept

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 1/20/16, Brad King <brad.k...@kitware.com> wrote: > On 01/20/2016 08:48 AM, Eric Wing wrote: >> I thought maybe setting the internal >> CMAKE_${lang}_COMPILER_ID_FLAGS_LIST or >> CMAKE_${lang}_COMPILER_ID_FLAGS >> to "-version" would fix this. >>

Re: [cmake-developers] CMake alternative language

Just to answer some of your questions on this... > > I think the first step is design brainstorming and discussion to see if > we can find something acceptable. > > IIRC one problem with earlier attempts at introducing Lua was that CMake's > dynamic scoping is difficult to reconcile with Lua's

Re: [CMake] XCode Generation Issue

On 1/21/16, David Morsberger wrote: > Eric, > > I went down a rabbit hole and pulled myself back out. I narrowed it down to > the following. > > We are using cmake to check if the linker supports -Wl,—as-needed. The test > compile (and link?) command cmake builds using ‘cmake

Re: [CMake] XCode Generation Issue

On 1/20/16, David Morsberger <d...@morsberger.com> wrote: > >> On Jan 19, 2016, at 10:11 PM, Eric Wing <ewmail...@gmail.com> wrote: >> >> On 1/19/16, David Morsberger <d...@morsberger.com> wrote: >>> Any help would be appreciated. >>> &g

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 1/19/16, Brad King <brad.k...@kitware.com> wrote: > On 01/18/2016 01:51 PM, Eric Wing wrote: >> So the good news is I have a basic add_executable working with Swift >> on Linux via the Makefile generator. >> >> It works with all Swift files, or intermixed

Re: [CMake] XCode Generation Issue

On 1/19/16, David Morsberger wrote: > Any help would be appreciated. > > In particular I’d like to know how the default compiler arguments are set > when ‘cmake -G Xcode’ is executed. The attached file contains the cmake test > compile extracted and reformatted from

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 1/15/16, Brad King <brad.k...@kitware.com> wrote: > On 01/15/2016 09:47 AM, Eric Wing wrote: >>> That is the same as for C++. See CMAKE_PARSE_IMPLICIT_LINK_INFO and >> >> I looked at this file, but I still havne't groked what I need to do >> with this y

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

(Ignore the last post. The last message sent accidentally before I was even close to done. Not sure why it sent. I must have accidentally discovered a hot key in Gmail. Everything is rewritten here.) Okay, I think I'm making some good progress. I got a trivial program built on Mac. I've now

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

Okay, I think I'm making some good progress. I got a trivial program built on Mac. I've now switched to Linux. I'm mostly there, but there are still some things that need to be done. More inline... https://github.com/ewmailing/CMake/tree/SwiftMakefile >> Anyway, I tried bumping up

Re: [cmake-developers] CMake alternative language

I am hesitant to add more fuel to the fire for this discussion because it has been discussed many times before through the years and my sense is that this isn’t what Brad is really interested in pursuing. I encourage you search the mailing list history. I’ll try to summarize (off the top of my

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 1/12/16, Brad King <brad.k...@kitware.com> wrote: > On 01/08/2016 06:15 PM, Eric Wing wrote: >> simple 'swiftc' integration going for ADD_EXECUTABLE, as described in >> the original post. > > Take the generator check out of Modules/CMakeDetermineSwiftCompiler.cmake &

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

> For the moment, I like swiftc over swift because it seems a lot > simpler. I hope this means the least changes for CMake right now. I need to correct myself on this. While I like swiftc for looking simpler, I'm actually thinking swift might be fewer changes since the file-by-file thing is what

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

>> If my hunch is correct, how do I tell CMake to ‘promote’ Swift as the >> correct tool? > > See the CMAKE__LINKER_PREFERENCE platform information variable. > There is also the LINKER_LANGUAGE target property. For C, C++, and > Fortran one generally chooses between C++ and Fortran to drive the >

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

> Yes. A few months ago I spent a few hours looking at the commands Xcode > uses to build Swift code. For reference, here are some notes I took > (not well organized): > > > MergeSwiftModule produces .swiftmodule files,

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

On 12/24/15, Eric Wing <ewmail...@gmail.com> wrote: >> set(SWIFT_BRIDGING_HEADER SwiftSDL-Bridging-Header.h) > > Quick addendum: Just realized the bridging header should probably be > per-target. > For reference, we have an Xcode specific, per-target variable

Re: [cmake-developers] Adding Swift support to CMake for Linux/Makefiles

> set(SWIFT_BRIDGING_HEADER SwiftSDL-Bridging-Header.h) Quick addendum: Just realized the bridging header should probably be per-target. -- 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

Re: [CMake] [cmake-developers] CMake IR

Disclaimer: My name is attached to the failed CMake/Lua attempt. In principle, I like the idea of what you propose. However, in practice, I think it might be too big and too ambitious. Here are some quick thoughts I have: - I am in the camp that I do not like the CMake language. And it is often

[CMake] Possible to dynamically construct macro/function names to invoke?

I would like to dynamically construct a macro or function name to invoke. I basically have a core CMake system I want users to be able to extend/plug stuff into without knowing about a lot of the core CMake implementation. Callback functions would be an easy way for me to accomplish this. As an

Re: [cmake-developers] Adding Swift support to CMake

On 7/7/15, Brad King brad.k...@kitware.com wrote: On 07/02/2015 07:54 PM, Eric Wing wrote: Thank you Brad. When you are ready, let me know how I can help next. I have basic support with the Xcode generator done. Please try out this commit: Add rudimentary support for the Apple Swift

Re: [cmake-developers] Adding Swift support to CMake

On 6/29/15, Brad King brad.k...@kitware.com wrote: On 06/25/2015 09:24 AM, Eric Wing wrote: I pushed up a couple of repos for everybody to try. Thanks. From that I was able to make some progress with getting CMakeDetermineSwiftCompiler to work. I've made two tweaks

Re: [cmake-developers] Adding Swift support to CMake

Hi Brad, I pushed up a couple of repos for everybody to try. First, I have my CMake changes I mentioned before. There are 2 commits. The first commit is the original simple hack. The second commit removes the hack part and tries to add a new language generator for Swift, using Java as a starting

Re: [CMake] iOS multi-arch library target and xcodebuild

* iOS toolchains I'm using: https://github.com/ruslo/polly (used to switch between different SDKs + to add some flags, like -std=c++11) Do you have to use a different toolchain for every different variant and different OS version? That's rather unfortunate if so. My current tweaks don't require

Re: [CMake] iOS multi-arch library target and xcodebuild

On 6/24/15, Ruslan Baratov via CMake cmake@cmake.org wrote: On 24-Jun-15 23:03, Bill Hoffman wrote: What is in the patched CMake? * workaround for bug: http://public.kitware.com/Bug/view.php?id=12506 * installing universal simulator + device library CMake already supports mulit-arch libraries

[cmake-developers] Adding Swift support to CMake

Hello all, I wanted to see if I could get the ball rolling on (Apple) Swift support for CMake. For more detail, here is the bug I’ve been chatting in: http://public.kitware.com/Bug/view.php?id=15401 Here is the summary: - For Apple developers, we need Swift support because it is going to be

[CMake] How do I set an Xcode property on the global/root project?

I have been successful at setting Xcode properties on specific targets with CMake via: set_property (TARGET ${TARGET} PROPERTY XCODE_ATTRIBUTE_${XCODE_PROPERTY} ${XCODE_VALUE}) But I have been unable to set properties on the global/root project. Is there a way to do this? Much of the time, I

Re: [CMake] How do I set an Xcode property on the global/root project?

On 6/14/15, Gregor Jasny gja...@googlemail.com wrote: Hi Eric, On 14/06/15 14:38, Eric Wing wrote: I have been successful at setting Xcode properties on specific targets with CMake via: set_property (TARGET ${TARGET} PROPERTY XCODE_ATTRIBUTE_${XCODE_PROPERTY} ${XCODE_VALUE}) But I have

Re: [CMake] cmake iOS application + framework link error

On 4/25/15, David Hirvonen dhirvo...@elucideye.com wrote: I'm hitting a link error when linking an iOS application with an internally created framework/library using the the CMake Xcode generator and an iOS toolchain. I've put together a minimal CMakeLists.txt example here:

Re: [cmake-developers] Support of codesign

Sorry, I'm also very late on this thread, but there was a suggestion that codesigning should be in CMake instead of CPack. I agree and also say it needs to be integrated as part of the build process when specified. Here's a real world workflow. I use JavaScriptCore in my Mac application which

Re: [CMake] xcode generator's use of explicitFileType vs lastKnownFileType

On 12/18/14, Radu Margarint rad...@raduma.com wrote: Greetings, I hope I'm asking this in correct place. I have recently been running into some issues using the xcode project files generated though cmake, and I have traced them down to PBXFileReference nodes using explicitFileType attributes

Re: [CMake] Copying shared libraries in a post-build step

On 12/9/14, Walter Gray chrysal...@gmail.com wrote: Hey all, I'm working on a module that will allow me to automatically copy all the required .dll files as defined by well-formed import library targets to the appropriate location (same folder for windows, Frameworks folder for OSX bundle,

Re: [CMake] Copying shared libraries in a post-build step

On 12/9/14, J Decker d3c...@gmail.com wrote: This is all handled by install. I already addressed INSTALL. I know you can change the directory. That is irrelevant to the point which I already addressed. Sounds really like you're working to build a package, which install is intended to do.

Re: [CMake] Copying shared libraries in a post-build step

Your scripts would still only work for one target... since you'd have to pick one to build the rest of the package around, so if I have a build product that has a dozen utilities, rather than having one place they can all work from, I have now to either duplicate all files to all runnable

Re: [CMake] CPack: .desktop files with tar.gz maker?

On 11/7/14, Clinton Stimpson clin...@elemtech.com wrote: On Friday, November 07, 2014 03:50:32 PM Eric Wing wrote: I have a build and packaging system where I can distribute (mostly) standalone apps for Linux desktop. I am using the default CPack installer which creates .tar.gz, .Z, and .sh

[CMake] CPack: .desktop files with tar.gz maker?

I have a build and packaging system where I can distribute (mostly) standalone apps for Linux desktop. I am using the default CPack installer which creates .tar.gz, .Z, and .sh files. I like this opposed to the .deb/.rpm package systems because users don't need root access to install/use my stuff

Re: [cmake-developers] [CMake] [ANNOUNCE] CMake 3.1.0-rc1 now ready for testing!

On 10/31/14, Gilles Khouzam gilles.khou...@microsoft.com wrote: We actually have a couple if extra changes that are not fully ready to be pushed upstream yet. ~Gilles Sent from my Windows Phone Since I have your attention, using CMakeMS, I hit what looks like a bug in the generation for the

Re: [cmake-developers] [CMake] [ANNOUNCE] CMake 3.1.0-rc1 now ready for testing!

On 11/4/14, Gilles Khouzam gilles.khou...@microsoft.com wrote: Hi Eric, Can you send me a little more details or an example that exhibits the problem? I'd be happy to take a look. Sure. I'll respond offlist for this. Thanks, Eric -- Powered by www.kitware.com Please keep messages

Re: [CMake] [cmake-developers] [ANNOUNCE] CMake 3.1.0-rc1 now ready for testing!

On 10/31/14, Gilles Khouzam gilles.khou...@microsoft.com wrote: We actually have a couple if extra changes that are not fully ready to be pushed upstream yet. ~Gilles Sent from my Windows Phone Since I have your attention, using CMakeMS, I hit what looks like a bug in the generation for the

Re: [CMake] [cmake-developers] Forwarding parameters to cmake through cmake-gui

Bump. With CMake 3.1 on the horizon, I was wondering if there was any progress on this. This would be really useful to me. I am basically invoking command line cmake.exe so I can pass all the right options, including my own CMake Initial Cache file. I ship an entire self-contained SDK of sorts

Re: [CMake] [cmake-developers] [ANNOUNCE] CMake 3.1.0-rc1 now ready for testing!

On 11/4/14, Gilles Khouzam gilles.khou...@microsoft.com wrote: Hi Eric, Can you send me a little more details or an example that exhibits the problem? I'd be happy to take a look. Sure. I'll respond offlist for this. Thanks, Eric -- Powered by www.kitware.com Please keep messages

[CMake] Using CMake to build an Emscripten output?

Not that I really have time to fix this, but I was experimenting with my C based codebase to see if I could compile it with Emscripten so it could run in a browser. After working around a lot of scary compiler bugs, I got it to work. But I invoked the build process by hand. So the next thing on

Re: [cmake-developers] [ANNOUNCE] CMake 3.1.0-rc1 now ready for testing!

Just curious, are the new WinRT changes the same exact changes from CMakeMS? And if the CMakeMS people are listening, I just want to say you guys did a terrific job! Thanks, Eric -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [CMake] [cmake-developers] [ANNOUNCE] CMake 3.1.0-rc1 now ready for testing!

Just curious, are the new WinRT changes the same exact changes from CMakeMS? And if the CMakeMS people are listening, I just want to say you guys did a terrific job! Thanks, Eric -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

Re: [cmake-developers] iOS support

On 9/23/14, Florent Castelli florent.caste...@gmail.com wrote: Hi! My company is organizing soon a hack week where each employee is able to work on any project he wants. So, I've decided to work with Cmake and improve support for iOS to help the product team getting rid of manual project

Re: [cmake-developers] iOS support

Thought of one more. I hate how the top, default target is ALL_BUILD. This is problematic for both Xcode and Visual Studio because when you use the big giant run button in the UI, the IDE is confused because ALL_BUILD is an aggregate target and not a real thing that can be run. At least for Xcode,

Re: [CMake] cmake 3.0.0 generating VS sln file default target machine type x86 (UNCLASSIFIED)

On 9/26/14, Su, Simon M CTR USARMY ARL (US) simon.m.su@mail.mil wrote: Classification: UNCLASSIFIED Caveats: NONE For some reason, when running cmake in VS2013 (express) x64 Cross Tools Command Prompt is not picking up the Visual Studio 12 2013 Win64 generator by default for this

[CMake] How do I create a dependency to copy (touched) resource files when building an executable?

I need to copy resource files from the source directory to the binary directory with the creation of my executable. I want CMake's dependency tracking to handle (re)copying these files whenever the source has been touched. Looking at other similar questions like:

Re: [CMake] How do I create a dependency to copy (touched) resource files when building an executable?

file only. Therefore, there is nothing to trigger the generation of the binary-dir file. Perhaps you wanted 'fooresources' to depend on the binary-dir file instead? Petr On Mon, Jun 30, 2014 at 3:20 PM, Eric Wing ewmail...@gmail.com wrote: I need to copy resource files from the source

Re: [CMake] How do I create a dependency to copy (touched) resource files when building an executable?

Okay, I switched just the add_custom_target DEPENDS to the binary directory (but left the add_custom_command alone). That seems to be doing what I need. I think I'm still not fully understanding the reasoning behind it, but problem solved I guess. Thanks, Eric On 6/30/14, Eric Wing ewmail

Re: [CMake] Cygwin drive paths are killing me

On 6/14/14, David Cole dlrd...@aol.com wrote: You are persistent... One of the keys to your success, I'm sure. But, out of curiosity... if you have Linux and Mac environments all set up already, why not build the Android stuff from one of those platforms?? Why go through all the pain of

Re: [CMake] Cygwin drive paths are killing me

I finally got it working. Here's a summary of my findings in case anybody finds this useful. (I think this will ultimately be useful info in trying to build a proper Android generator for CMake.) - I ditched Cygwin. (But I learned that CMake later on for Unix Makefiles complains about Cygwin

Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?

Thanks everybody for the answers. I finally got it working more or less to my satisfaction by writing it manually. Mike, I grabbed some of your install stuff. Thanks for that. J Decker, thanks for reminding me about CMAKE_CFG_INTDIR. I knew about it, but it's easy to forget. (That's why I didn't

Re: [CMake] Mac @loader_path for @rpath questions

On 5/24/14, clin...@elemtech.com clin...@elemtech.com wrote: - Original Message - I have a bunch of libraries and frameworks that properly use @rpath. Now I am trying to build an application that uses those library and frameworks via CMake. From this blog:

[CMake] Cygwin drive paths are killing me

I am currently in this unholy trinity of needing to use Android on Windows through Cygwin. Basically, the Android NDK requires Cygwin if you want to run it on Windows. I'm using my fork of the Android-CMake toolchain originally from OpenCV and trying to generate Unix Makefiles with CMake. I

Re: [CMake] Cygwin drive paths are killing me

Thanks everybody for the replies. - I am using the native CMake, not the cygwin one. I didn't realize there was a difference. I'll try that and hope that works. - The Android NDK page itself says Cygwin 1.7 is required. Maybe it is BS, but I don't know. Required development tools * For

Re: [CMake] Cygwin drive paths are killing me

So I tried the Cygwin CMake, and while it allowed me to remove most of my hacks, the final Makefile was still not usable because it appears the standalone gcc wants a Windows path and not /cygdrive/. So let's pretend I can do this without any Unix tools... - Am I still generating Unix Makefiles?

Re: [CMake] Cygwin drive paths are killing me

Yes, I will probably try MSYS next. Then I will see if I can remove MSYS entirely. (Though I'll need to rewrite my helper script which is mostly Perl.) I'll look into that standalone Make 3.8.1. The helper script basically does the CMake generation 3 times (armeabi, armeabi-v7a, x86). The script

Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?

On 5/23/14, Dan Kegel d...@kegel.com wrote: You can add the directory containing the 3rd party DLLs to the global PATH environment variable, I bet. So I'm looking for a CMake way to deal with this. I don't want to change the system environment. My stuff is highly distributed among lots of

Re: [CMake] What do Visual Studio users do so they can run/debug their programs when using 3rd party .dlls?

On 5/23/14, Dan Kegel d...@kegel.com wrote: On Fri, May 23, 2014 at 4:38 PM, Eric Wing ewmail...@gmail.com wrote: On 5/23/14, Dan Kegel d...@kegel.com wrote: You can add the directory containing the 3rd party DLLs to the global PATH environment variable, I bet. ... I just want a work-out

Re: [CMake] CMake for Android projects

So I have 4 examples I actually tried to document. These all use my fork/derivative of the Android-CMake toolchain, which I believe comes from OpenCV. (It had grown stale with later NDKs and I hit problems). All of these rely heavily on the external NDK module system (NDK_MODULE_PATH). The first

Re: [CMake] Linking to Mac OS X frameworks

On 4/17/14, Aggelos Kolaitis neoagge...@gmail.com wrote: Short: Is linking to Mac OS X frameworks with Xcode generator totally broken, or am I just doing something wrong? Long: I use CMake as the build system for my project[1], and I use this [2] module to find SDL2 in the user's system.

Re: [CMake] Write CMakeLists in another programming language?

On 4/3/14, Clark Wang dearv...@gmail.com wrote: I've been using cmake for some time but still I'm confused about the syntax. Following are 2 examples from me: - http://www.cmake.org/pipermail/cmake/2013-September/055924.html - http://www.cmake.org/pipermail/cmake/2013-October/056036.html

  1   2   >