[cmake-developers] [CMake 0013556]: Ninja: Does not support 'ninja edit_cache' if cmake-gui does not exist
The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=13556 == Reported By:Yuchen Deng Assigned To: == Project:CMake Issue ID: 13556 Category: CMake Reproducibility:always Severity: major Priority: normal Status: new == Date Submitted: 2012-09-23 07:47 EDT Last Modified: 2012-09-23 07:47 EDT == Summary:Ninja: Does not support 'ninja edit_cache' if cmake-gui does not exist Description: When running 'ninja edit_cache', I can't select / set any option. Because I have no chance to select / type anything. It's over, don't wait for user input. == Issue History Date ModifiedUsername FieldChange == 2012-09-23 07:47 Yuchen DengNew Issue == -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Using the internal Code::Blocks builder
Am Donnerstag, 6. September 2012 um 09:24:39 schrieb Benjamin Eikel: Am Mittwoch, 5. September 2012 um 22:29:59 schrieb Bill Hoffman: On 9/5/2012 3:11 PM, Benjamin Eikel wrote: That might become a problem. I tried codeblocks --build --target=MyTarget MyProject.cbp which works and builds the specified target inside the project. But that opens a log window. I have not found a possibility to execute that without a display, yet. http://www.codeblocks.org/docs/manual_en.pdf IDE CodeBlocks can be executed from the command line without a graphic interface. In such a case, there are several switches available for controlling the build process of a project. Since CodeBlocks is thus scriptable, the creation of executables can be integrated into your own work processes. codeblocks.exe /na /nd --no-splash-screen --built name.cbp --target=’Release’ I also read this, but it is not true. Even with all these command line switches a window appears showing the build log. If I set the DISPLAY environment variable to an invalid value, I get the error message Error: Unable to initialize gtk, is DISPLAY set properly?. There is also an old forum discussion about this: http://forums.codeblocks.org/index.php/topic,9731.0.html I asked for help in the Code::Blocks forums: http://forums.codeblocks.org/index.php/topic,16892.new.html -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
Re: [cmake-developers] Exporting dependent library targets in multiple export sets
On Friday 21 September 2012, Alexander Neundorf wrote:
On Thursday 20 September 2012, Brad King wrote:
On 09/20/2012 12:20 PM, Alexander Neundorf wrote:
if(NOT TARGET Foo)
if(CMAKE_FIND_PACKAGE_NAME)
set(${CMAKE_FIND_PACKAGE_NAME}_FOUND FALSE)
What happens if other imported targets have already been defined?
Then the targets file will have been partially loaded.
Yes.
Is this a problem ?
If some find-module searches several libraries, and finds only some of
them, those FOO_LIBRARY variables which have been found also stay set, and
are not reset, but the overall result is NOTFOUND.
set(${CMAKE_FIND_PACKAGE_NAME}_NOT_FOUND_MESSAGE
The required target Foo does not exist !)
else()
message(STATUS
Warning: the required target Foo does not exist !)
endif()
endif()
or SEND_ERROR or FATAL_ERROR ?
I think FATAL_ERROR. It is always easier to lessen this later.
Ok.
This is now in the export-sets-2 branch on stage, including a basic test.
Comments ? Ok to merge into next ?
Alex
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
[cmake-developers] export() generates files at configure time
Hi, In investigating moving the linking-relevant API from cmTarget to cmGeneratorTarget, I found that the export() command generates target files at configure time, not at generate time. If it generated the files at generate time, I would be able to make progress moving the linking-relevant API. I can't think of any reason for the fact that it currently generates the files at configure time to be useful. Any objection to changing that? Thanks, Steve. -- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
