Page 1 of 1

projectize a bunch of source and target files

Posted: Wed Sep 08, 2010 8:15 am
by MyTrial
Hello

I am not firm with the use of thr "project" handling in the ide and wanted to start with that. But i think i need a little help. :)

First i went a little angry, because when i take a existing target file and insert that as default target in the project the defined options would not be taken within, so i have to do the job twice. It would be nice to use the "old" options by inserting in the project.

Next i get all running if i have a project with one target and a bunch of source files.

When i use a more complicated bunch of source and target files i do not get it working. As explainment: I have a bunch of pbi files with many functions which are used by a bunch of pb target files. Not all target files have the same compiler options, some are console programs and some are gui programs. This i get only to work if i use a separate project for each target. But if i change a pbi file which is used in more than one target (and therefor project), not all targets would be compiled. And it would be good to have all projects i have to build as one project, because it is one project. Is that possible? If yes, can someone explain me how to use that or have a link for a description of the use? Thanks.

Sigi

Re: projectize a bunch of source and target files

Posted: Sat Oct 02, 2010 10:29 am
by MyTrial
Hope my english is not so bad, that I got no answer or information but many looking people. ;)

To understand my problem (or wishes) better, I put that in a little graphical explainment.

A sample structure of source with some background procedures in PBI files and some resulting programs as console and as gui (window) programs.

Code: Select all

001.pbi -----------------------+--- p_001.pb --> p_001 console
002.pbi ---+-------------------|---
           |     +-------------|---
           |     |     +-------|---
           |     |     |       |
           |     |     |       +--- p_002.pb --> p_002 gui (window)
           +-----|-----|-------|---
003.pbi -----+---|-----|-------|---
004.pbi -----|-+-|-----|-------|---
005.pbi -----|-|-+-----|-------|---
006.pbi -----|-|---+---|-------|---
007.pbi -----|-|---|-+-+-------|---
008.pbi -----|-|---|-|-+-------|---
009.pbi -----|-|---|-|-|-+ ----|---
             | |   | | | |     |
             | |   | | | |     +--- p_003.pb --> p_003 gui (window)
             +-|---|-|-|-|-----|---
             | +---|-|-|-|-----|---
             |     | | | |     |
             |     | | | |     +--- p_004.pb --> p_004 console
             |     +-|-|-|-----|---
             |     | +-|-|-----|---
             |     |   | |     |
             |     |   | |     +--- p_005.pb --> p_005 console
             +-----|---|-|---------
                   +---|-|---------
                       +-|---------
                         +---------
Now when I edit the "001.pbi" all resulting programs should be new compiled. If I edit "002.pbi" only the "p_001.pb" and the "p_002.pb" should be new compiled. And so on.

Hope that is "brainable". ;)

A information: I use the #PB_Compiler_Date information as additional part to the program version. So it is not possible to write a batch file and compile all resulting programs thru with some command line options of the compiler (I didn't have a look to that). If that would be done, a program would get a new #PB_Compiler_Date information, but there is nothing new inside.

Sigi