🚀 go-pugleaf

Rob,

I started off using packages but I was struggling to get everything 
straight.  When working in the IDE I created a project group with the 
package and IDE.  I had trouble keeping track of which project was 
active and I could not find a way to run (F9) when the package was the 
active project.  I also seemed to run into trouble with the package not 
being rebuild when I ran the exe.  I changed the Build control to 
"Rebuild as needed" but I still found it was not always rebuilt correctly.

I really liked the idea of using packages because I thought it would 
help me keep my dependencies straight.  I have a good idea how I would 
setup my automated release builds with packages.  Can you give me any 
other ideas on how you work with them in the IDE?

I guess this really is not a commandlinetools question anymore :(

Mark

Rob Kennedy wrote:

> Use packages. My rule is that every source file must be a member of one 
> and only one project and a source file only ever gets compiled when its 
> project gets compiled.
> 
> Just because a unit is a member of a package doesn't mean that the 
> package needs to be installed in the IDE or that the program that uses 
> the unit needs to use run-time packages.
>