MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012493CMakeCMakepublic2011-10-05 10:292016-06-10 14:31
ReporterMaxim Ignatenko 
Assigned ToKitware Robot 
PrioritynormalSeverityfeatureReproducibilityN/A
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 2.8.6 
Target VersionFixed in Version 
Summary0012493: Erlang/OTP support
DescriptionMost complete effort to write Erlang support for CMake could be found here: https://github.com/okeuday/generic-erlang-port--driver-/tree/master/CMake/erlang [^]
But there's one issue: it does not generate *.app file for batch of *.beam files. Instead of trying to link *.beam files in one executable (which has no sense) add_executable() should generate *.app file from user-supplied template or based on target properties.
Currently I'm trying to do it by setting CMAKE_Erlang_LINK_EXECUTABLE to "cmake -P gen_app_file.cmake ...", but this is a bit ugly, since new cmake process has no access to parent's data and all parameters need to be supplied as command line arguments.

So, feature request is:
1) make it possible to use user-defined CMake function instead of CMAKE_<LANG>_LINK_EXECUTABLE
2) import mentioned files into CMake distribution (after some adaptation)
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-10-05 10:29Maxim IgnatenkoNew Issue
2012-08-11 11:38David ColeStatusnew => backlog
2012-08-11 11:38David ColeNote Added: 0030309
2016-06-10 14:28Kitware RobotNote Added: 0041908
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030309)
David Cole   
2012-08-11 11:38   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041908)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.