This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | CMakeLists.txt doing all work in a subdir | ||
---|---|---|---|
Product: | cnd | Reporter: | chunkyks <chunkyks> |
Component: | -- Other -- | Assignee: | Alexander Simon <alexvsimon> |
Status: | CLOSED FIXED | ||
Severity: | blocker | CC: | Hamsi |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 187623, 192728 | ||
Attachments: | svn status output after netbeans configured my project via cmake |
Description
chunkyks
2009-10-24 19:55:14 UTC
Created attachment 90052 [details]
svn status output after netbeans configured my project via cmake
Changing to all platforms - I see the same behaviour on systems other than the original one I tried. I share the joy at seeing support for CMakeLists.txt. Very cool. Good job, team! While I also share your wish that NetBeans build such projects in a subdirectory, instead of in the source folder, I would prefer that the build subdirectory have a more specific name, based on the currently selected configuration and possibly the toolcollection and/or other developmenthost. Thus, I would like to see NetBeans use build instructions something like: 1) cd <projectfolder>; 2) mkdir build; cd build 3) mkdir <configuration>; cd <configuration> 4) mkdir <toolcollection>-<developmenthost>; cd <toolcollection>-<developmenthost> 5) cmake ../../.. 6) make Any variation of this would be most acceptable to me. It would probably be best for NetBeans to essentially mirror the build commands it follows for "managed" projects. I recognize that, at present, the notions of <configuration>, <toolcollection>, and <developmenthost> are less clear for cMake-based projects than they are for managed Makefile projects, but I'll post a separate feature request that the <configuration> get passed to CMake on its command line: 5) cmake -DCMAKE_BUILD_TYPE=<configuration> ../../.. along with a few other relevant options. CMake developers actually recommend this usage mode. I have found it to be better supported and having a lot of advantages as opposed to in-tree build. Besides that, using in-tree cmake with netbeans is currently a non-working scenario together with version control, since all the build artefacts are presented for SVN checkin. Bah - nothing after the latest updates. Unfortunately this cmake plugin is unusable with a version control. All new files created by cmake in the same dir are treated by the SVN plugin as "new" files, and it wants to commit them all. Back to KDevelop :) Other same enhancement: http://netbeans.org/bugzilla/show_bug.cgi?id=187623 fixed, change set: http://hg.netbeans.org/cnd-main/rev/33e822320dd9 Now IDE can run configure in subfolder for: - "configure" shell script - "CMakeLists.txt" cmake script - "*.pro" qmake script Integrated into 'main-golden', will be available in build *201012010001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/33e822320dd9 User: Alexander Simon <alexvsimon@netbeans.org> Log: fixed Bug #175374 CMakeLists.txt doing all work in a subdir Awesome, it works great. Thank-you very much Should that behaviour be made the default? I first ran this with "automatic", and it spread the same cruft through the sub dir I suspect that the best thing to do would be to make cmake and qmake work in a subdir by default, but make autoconf work in the same level by default. Either way, I'll close this as resolved and open a new bug for discussion. |