patch for custom makefile projects

Hendrik Kueck kueck at cs.ubc.ca
Mon Oct 20 00:04:02 UTC 2003


I made some changes to the custom makefile project part:

1) Added support for multiple build configurations (i.e. multiple sets 
of environment variables).
(see http://bugs.kde.org/show_bug.cgi?id=49650 )
To this end, I extended the Project Configuration/Build/Make dialog and 
also added a Build menu entry for choosing the active set of environment 
variables.

2) Added a way to choose the active directory for a project, i.e. the 
directory where new classes get created.
(see http://bugs.kde.org/show_bug.cgi?id=64860 )
I added a context menu for directories in the file tree/file selector 
for this.

Also, while working on 1), I changed the environment variable widget 
which is also used in the automake part (and maybe elsewhere):
- Renamed the "Add/Edit" button to "Add/Copy" because that is what it is 
doing.
- Added a new "Edit" button that allows to edit existing variables 
without copying them.

It would be great if someone with CVS access could find the time to look 
at the patch, test and submit it.

There are a few more things that I would like to change in the custom 
project part but which need to be discussed:

There currently is a radio button menu in Project Configuration/Build 
for selecting either make or ant.
There is however no special support for ant at all. Selecting 'ant' 
simply means to ignore the settings in the 'Make' tab and to just invoke 
'ant' for building the project.
Because there already exists an ant project part with actual support of 
ant, I suggest to either
- make the custom makefiles part 'make only', as the name implies and 
thus get rid of the radio menu.
- or change the 'ant' radio button label to 'other build tool' and add a 
text field to choose an arbitrary build tool.

When creating a new custom project, it offers to scan the project 
directory and import existing files. The message box asks:
   "This project does not contain any files yet.
    Populate it with all C/C++/Java files below
    the project directory?"
However, when selecting  'yes', _all_ files in the project directory and 
  subdirectories get added to the project. That is, all object files, 
data files, ... .
I feel that this should be changed to only add files with certain 
extensions to the project. The question however is, what extensions 
those  should be? Just hardcoding a bunch of fixed extensions is not 
really a great solution but probably better than just adding everthing.

Cheers,
Hendrik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch_customproject_multienvs.bz2
Type: application/octet-stream
Size: 6841 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20031020/6791d5d5/attachment.obj>


More information about the KDevelop-devel mailing list