Feature #4336 2008-10-20 22:01

shwareguy

auto-conf/make import as project(s)

This would create a workspace file in a chosen directory with projects named after the package being imported for each host-native, host-variant, or cross compiler on the system the user selects and the package supports, e.g. gdb-x.y.z_mingw- gcc-a.b.c_native.cbproj, gettext-x.y.z_SuSE-gcc- a.b.c_SuSE-gcc-d.e.f.cbproj, or coreutils- x.y.z_redhat-gcc-a.b.c_debian-gcc-m.n.o.cbproj. Subdirectories for configuration info and build / packaging staging for each project would also be created.

It would create in each project Release and Debug aliases for each exe/dll/lib build and package target found in top-level autoconf 2.13 or 2.5+ and automake 1.x .ac, .am, or .in files, for most GNU packages, and from cygnus / redhat configure scripts for those GNU packages that still use them, with recursion into subdirectories as required. Tool dependancies to be resolved, tool flags used, environment variables and compiler defines, etc., should also be accounted for, ideally from a database where .cbproj's for each tool already converted is maintained.

This is just a basic synopsis. Exact features would need to be hashed out, obviously, by people more familiar with the bash/m4/sed trio than I but overall goal is to make life easier for those people maintaining or modifying GNU sources to be able to use CodeBlocks for creating a variety of distribution binary and source packages from a given current source set, without worrying as much they've run configure or make improperly for each target.

Category

Plugins

Status

Open

Close date

 

Assigned to