Why do Linux IDEs create so many extra files?

stodge · 05-02-2003, 05:14 PM

I installed Anjuta and created a test project that was a standard static library (console based). When Anjuta finished creating the project there were 31 files! 31? What the hell for? I only want to create an empty project so I can import a bunch of files for myself.

Sorry, rant over!

Is there anything out there that is free and more like Visual Studio where it only creates a handful (or less) files for an empty new project?

Thanks

acid_kewpie · 05-02-2003, 05:20 PM

the point of those files is for configuring, compiling i18n, and other such standard features that are required for a normal source application, that's the point of it...

stodge · 05-02-2003, 06:29 PM

Whatever happened to the days of a single makefile?

jailbait · 05-02-2003, 08:29 PM

Gone With the Wind

acid_kewpie · 05-03-2003, 03:01 AM

if you want a single makefile, make it... having all the standard files means that in theory once you write your code you just tar it all up and there's a finished, fully GPL'd product ready to release

nakkaya · 05-03-2003, 03:18 AM

or if you only want the file you created use emacs if you configure it correct you will gaim 10x more speed elastisity than any other exeisting ide.

stodge · 05-03-2003, 12:23 PM

I've already started working on the Makefile; I figure that's the best solution. I'm just frustrated at not having an alternative to being forced to follow the GPL route. Ah well.....

jtshaw · 05-03-2003, 12:38 PM

You can always write non-GPL software but you have to find it reasonable that a GPLed IDE is probably going to create GPL focused software. Just because you have all those extra files doesn't mean you are licensing your stuff out via the GPL, that is ultimately your decision. Becareful writting commercial code with the free IDE's btw. Many of those IDE's require you to pay for them if you are writting code you plan to make money off of yourself, which is only fair.

John