OMNeT++/OMNEST Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000031OMNeT++IDE / genericpublic2008-12-07 15:242017-03-02 16:15
Reporterbaumgart 
Assigned Torhornig 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version4.0b8 
Target VersionFixed in Version5.1 
Summary0000031: Better Makefile support for compiling without IDE
DescriptionAs far as I understand, the prefer way to generate Makefiles for projects with src/ directory is as follows:

The IDE creates auto-generated Makefiles with opp_makemake in PROJDIR and PROJDIR/src. Additionally you can export a ./makemake script to generate these Makefiles without IDE.

I would prefer the way how INET does this currently: Have a Makefile in PROJDIR which calls opp_makemake to generate the Makefile in PROJDIR/src.
Then the IDE should only create the Makefile in PROJDIR/src and have an option to export the "Makefile-generation-Makefile" as PROJDIR/Makefile. Benefit: You can simply call make in the PROJDIR to compile the project from the commandline. This top-level Makefile could also be extended e.g. to generate doxygen documentation.

This even works with the current IDE already, if you manually set the build PATH to PROJDIR/src - but maybe this should be the default behaviour for new projects as well. BTW, the simulation binary (or better a symbolic link to the binary) is always generated in PROJDIR/src/ . It would be cleaner to have this in PROJDIR or PROJDIR/bin.




TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0000098)
rhornig (administrator)
2008-12-20 17:36

We had problems with the way INET was/is configured. If the top level makefile automatically generates all makefiles (including himself) then the IDE has serious truble using this makefile structure. i.e. first the IDE genrates its own makefiles then calls the top level makefile which overwrites everything the IDE has written. The other problem is, that we do not want to distribute automatically generated makefiles (they might contain absolute paths). Now if the toplevel makefile is automatically generated, we should not distribute it. But if not distributed what should be called from the command line to create the makefiles after a distribution was first unpacked? We will refine the build process in a later version.
(0001346)
rhornig (administrator)
2017-03-02 16:15

This is no longer an issue with 5.1 makefiles

- Issue History
Date Modified Username Field Change
2008-12-07 15:24 baumgart New Issue
2008-12-20 17:36 rhornig Note Added: 0000098
2008-12-20 17:37 rhornig Status new => postponed
2008-12-20 17:37 rhornig Resolution open => suspended
2017-03-02 16:15 rhornig Note Added: 0001346
2017-03-02 16:15 rhornig Status postponed => closed
2017-03-02 16:15 rhornig Assigned To => rhornig
2017-03-02 16:15 rhornig Fixed in Version => 5.1


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker