On 2012-11-09 22:44, waldo kitty wrote:
>
> yes, sorry...
OK, I currently have the following layout. I like to keep paths to
libraries and projects as should as possible. I used to use
/opt/fpc-x.y.z/ and /opt/laz/ etc. /opt and /home is normally in
separate partitions so that if I update (reinstall) my Linux OS, I can
format / and my /opt and /home partitions are not affected. This has
worked very well for many years.
But for some reason I decided with my latest PC to only have two
partitions. / and /home so now all my programming work is in my home
directory. Here is my directory layout.
$HOME/devel/
is where all my programming content lives. I then have the following
structure under that directory.
Most used frameworks are top level to shorten directory paths - like for
mseide or maximus.
|-data [Firebird *.fdb database files etc.]
|-docs
|---inf [RTL,FCL,LCL,fpGUI,tiOPF etc help for DocView]
|---pdf [docs from FPC but in PDF format - hardly used]
|-<client_name> [I group paid work by client and project]
|---<project_name>
|-fpc-2.6.0 [I have one ~/.fpc.cfg for all FPC versions]
|---src
|---x86_64-linux
|------bin
|------lib
|------...
|---i386-linux
|------bin
|------lib
|------...
|---i386-win32
|------bin
|------lib
|------...
|-fpc-2.7.1
|---... [same structure as v2.6.0 above]
|-lazarus [this is trunk]
|-lazarus-0.9.30.4 [stable release for production work]
|-mseide [I sometimes use this IDE too]
|-fpgui
|-tiopf2
|---src
|---website
|---supportapps
|-tiopf3
|---src
|-fptest [Free Pascal fork of DUnit2 project]
|-3rdparty
|---onguard
|---synapse
|---fpc_docs [FPC Docs subversion checkout]
|---pwu
|---dcpcrypt
|---zeos
|---ibx
|-personal
|---<any_private_projects>
|-tests
|---<any_test_projects>
used for testing components or bugs reports
For my virtual machines (I use VirtualBox), I'll setup a share which
points to $HOME/devel/
The above setup is on my actual PC running OpenSUSE. I'm moving all my
development work into virtual machines. So I'll end up with three
development VM's - one for 64-bit Linux, and one for 32-bit Windows and
one for 64-bit FreeBSD. All of these are already setup, except for the
64-bit Linux VM - the last setup to be completed this week.
I then have other testing VM's for 32-bit Linux, 64-bit Windows,
ReactOS, Solaris etc. Some have a FPC compiler setup, others are just
for testing cross-compiled apps.
The nice thing of having your development work setup as VM's, is that if
you have hardware troubles, I can move the VM's to another system,
install VirtualBox, and continue as normal - until my main desktop PC is
fixed.
> also copy some projects over to my OS/2 box and compile over there with fpc
> directly so everything has to be the same on both boxes as far as the
> directory
> layout goes...
With virtual machines (like VirtualBox), I can create a virtual shared
drive. So I could actually setup all my development software on that,
and simply add it as a second drive to any of my VM's.
And that is it! Hope it helps.
Regards,
- Graeme -
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
