I want a "source collection" !!!!

Hi,

I want to create multiple projects which share source code files (units).

I am tired of having to add all these units to each new project I start !!!

So I want to do all that once. I want to create a "collection of source
files".

The "collection of source files" knows exactly where each unit name is
located.

That means:

1. The unit filenames can easily be added to any uses clause in any unit
that is part of the project without the compiler bitching that it can't find
a unit (*.pas).

2. The compiler will generate compiled units (*.dcu) and store them in the
same folder as the source files by default !

3. The compiler will find any compiled unit (*.dcu) which is part of the
"source collection".

Now comes the most important part of all.

The "source collection" can then be added to the project file. The project
file stores which source collection (folder and filename) it uses.

This is very important for the history.

For example a year from now I simply want to open that project file and it
will simply compile and build and run... all source codes could be old by
then and have newer versions but I don't care about that... I want to have
the exact same old version as a year ago for example to find bugs/problems
or when next versions fucked up whatever.

I do not want to use a "automate/software" versioning system... just a
manual versioning system which I can do myself.

Delphi does not have such a feature as described above.

The only features which I found so far which come close but dont cut it are:

1. Search path <- Tired of it... must add many many many folders for each
project bleh.
2. Library path <-This is the "environment" and not "per project'. I dont
want a environment with multiple versions of the same technology supported
that would be very confusing and dangerous when making changes... those
might up in wrong version.
3. Packages <- See point 2 above. "Link-In Packages" can not be added per
project !! the sources files end up in the library path !!! see point 2
above !.

Borland mostly sees packages as binary thingies... like dll's etc.

I don't want any dll's etc... I want a big executable.

Here is the scenerio to illustrate the current problem with delphi 7:

c:\tech\blue\version 0.01\unit_blue.pas
c:\tech\blue\version 0.02\unit_blue.pas

c:\tech\red\version 0.01\unit_red.pas
c:\tech\red\version 0.02\unit_red.pas
c:\tech\red\version 0.03\unit_red.pas

A project 0.02 would need to add the last two folders... if one has like 50
folders that's a drag and I am tired of it it's stupid ;)

So a package you say ? useless.

Package 0.01 includes:
c:\tech\blue\version 0.02\unit_blue.pas
c:\tech\red\version 0.03\unit_red.pas

Click compile and the folders will be added to the library path.

Now comes the problem.

Technology evolves:

c:\tech\blue\version 0.01\unit_blue.pas
c:\tech\blue\version 0.02\unit_blue.pas
c:\tech\blue\version 0.03\unit_blue.pas
c:\tech\blue\version 0.04\unit_blue.pas
c:\tech\blue\version 0.05\unit_blue.pas

c:\tech\red\version 0.01\unit_red.pas
c:\tech\red\version 0.02\unit_red.pas
c:\tech\red\version 0.03\unit_red.pas
c:\tech\red\version 0.04\unit_red.pas

Suppose one wants to create another stable package.

Package 0.02 includes:
c:\tech\blue\version 0.05\unit_blue.pas
c:\tech\red\version 0.04\unit_red.pas

Now big fucking problem occurs.

The library path would be updated with these two folders and there are now
two units with the same name on the library path.

Which one will a new project use ?

Maybe the library path doesnt even allow units with the same name twice on
the library path etc...

The only alternative would be to add the source files to the project's
search path and as I said at the beginning of this post I am tired of it !!!
I want to do that once and then re-use the "source collection" in multiple
projects.

So the problem is that the environment gets infected with this ***.

That's why I want a "source collection" which can be simply added to a
project instead of the fucking environment. Ofcourse a source collection
could be added to the environment as well as an extra option ;) and ofcourse
easily removed as well.. same goes for project.

(or a package which can be added to a project only and all search
paths/library paths automatically set for that project only !!!!!!!!!! )

I could simply "cut out" the part where the search path begins in a project
file and simply cut and paste that to a new project file etc... but still
it's pretty nasty. It's not a clean solution etc...

Bye,
Skybuck.


.

Quantcast