Re: [cmake-developers] iOS support
Thanks for the detailed information. My hackweek starts on Monday and I'll start working on these issues then. I'll work on finding a way to unify toolchain files for simulator and devices first. I don't think I'll try to work on iOS8 features since my company is shipping for iOS6 and there are so many things to do :) Though, I'm not really an iOS developer, there's probably a ton of things I'll miss. But I have great devs in my company and I'm sure it'll be okay! I'll keep you updated of my progress during the week and hopefully, I won't have to call for help here too often :) /Orphis On 1 Oct 2014 01:42, Eric Wing ewmail...@gmail.com wrote: 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, a bunch of options change dynamically based on the type of target selected and building/launching to the device/simulator is not an option when on an aggregate target. It's an annoyance because it interferes with the normal workflow for those familiar with the IDEs. And it's an annoyance for those who are not familiar with the IDEs because the big giant buttons do nothing and they don't understand the IDEs well enough on how to correct the issue. (It's also more work invoking xcodebuild and msbuild because you can't rely on the default targets.) Thanks, Eric -- 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-developers
[cmake-developers] [CMake 0015185]: Allow for partial customization of WiX.template.in
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15185 == Reported By:Richard Ulrich Assigned To: == Project:CMake Issue ID: 15185 Category: CPack Reproducibility:always Severity: feature Priority: normal Status: new == Date Submitted: 2014-10-01 11:09 EDT Last Modified: 2014-10-01 11:09 EDT == Summary:Allow for partial customization of WiX.template.in Description: At the moment I have my own copy of WiX.template.in in my project specific Modules directory. In the discussion of http://public.kitware.com/Bug/view.php?id=15165 I realized that it would be beneficial, if there was a way to only extend WiX.template.in without having to completely maintain it myself. * One approach would be to include a custom.wxi file in WiX.template.in and ship an empty custom.wxi file that could be overridden. * Another approach would be to extend the patching mechanism to the Product tag. As at the moment it only work on tags that are generated by the cpack c++ code, it's not just a matter of adding an ApplyPatch() line in the correct place. Things I customized in my WiX.template.in: * Product.Language=!(loc.LANG) - this could be tricky. It's not covered by both of the above approaches. - shipping also a default lang.wxl file could make it work. * Adding Components or ComponentRefs that need to be in the Product tag. - this is the easy part, solved by both approaches. * Adding a second UiRef (WixUI_ErrorProgressText) == Issue History Date ModifiedUsername FieldChange == 2014-10-01 11:09 Richard Ulrich New Issue == -- 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-developers
Re: [cmake-developers] Extracting target metadata, IDE integration
On Wed, Sep 24, 2014 at 6:51 PM, Aleix Pol aleix...@kde.org wrote:
On Wed, Sep 24, 2014 at 3:55 PM, Brad King brad.k...@kitware.com wrote:
On 09/22/2014 07:15 PM, Aleix Pol wrote:
{
version: 1.0,
targets: [...]
}
Yes. The version number could either be maintained as its own
thing, or just the CMake version number could be used. Either way
the Help/variable/CMAKE_OUTPUT_PROJECT_TARGETS.rst documentation
should specify the format of each version.
BTW, the phrase output project targets is not particularly
clear without knowing the feature already. Perhaps some other
name like CMAKE_EXPORT_IDE_METADATA would be better?
I've never worked with those, but it sounds like it would make sense.
What about:
{
version: ..
configurations: {
{ name: Debug, targets: [...] },
{ name: Release, targets: [...] }
}
}
Yes, something like that. I think you meant to use [] rather than
{} around the list of configurations. In the case that there is
only one configuration for the generator we should still use a
list but have only one entry.
Sure :)
-Brad
Hi,
Here's another iteration of the patch [1].
Basically adopts the possibility to move some information to depend on the
configuration. Currently it's only showing the I source files, I guess
location, directory and installed should be moved as well. Correct?
Aleix
[1]
New patch:
http://proli.net/meu/kdevelop/0001-cmake-Add-option-to-generate-target-metadata-for-IDE.patch
New output: http://proli.net/meu/kdevelop/ProjectTargets.json
Bump.
I'm very interested in getting this in and iterating forward.
Any comments? How do changes get integrated?
Aleix
--
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-developers
