|
|
Home » Developing U++ » Releasing U++ » Working on new release system...
Working on new release system... [message #20365] |
Sat, 14 March 2009 12:09 |
|
mirek
Messages: 14039 Registered: November 2005
|
Ultimate Member |
|
|
I have started much needed work on new flexible release system, I have decided to put some description and notes here, as sort of "release system blog".
First, Win32 build system.
It will be supposed to run on "U:" drive, with "U:\upp.src" being the svn trunk.
Build method used will MSC9.
Now important think, also for other releases. We need to finally have some means describing what belongs to the release. That is why
in U:\upp.src\uppsrc (which is normal svn uppsrc) folder are now files:
packages - contains a list of subdirectories of u:\uppsrc\uppsrc that are supposed to be in release, including "deep" subdirectories
packages1 - same, but without subdirectories
assemblies - list of assemblies to put into release excluding uppsrc (means, examples, reference, tutorial, bazaar).
(more to follow...
|
|
|
Re: Working on new release system... [message #20367 is a reply to message #20365] |
Sun, 15 March 2009 01:00 |
|
luzr wrote on Sat, 14 March 2009 13:09 | I have started much needed work on new flexible release system, I have decided to put some description and notes here, as sort of "release system blog".
First, Win32 build system.
It will be supposed to run on "U:" drive, with "U:\upp.src" being the svn trunk.
Build method used will MSC9.
...
|
How about to ask the user where need unpack upp.src? By default will be nice in "U:\upp.src". Same situation will be nice add for examples, reference, tutorial and bazaar! Not only for MyApps!
|
|
|
|
Re: Working on new release system... [message #20430 is a reply to message #20370] |
Wed, 18 March 2009 11:36 |
|
mirek
Messages: 14039 Registered: November 2005
|
Ultimate Member |
|
|
Nightly builds should now be working.
The key point to define builds is in svn:
uppbox/Scripts/all
and this script calls several subscripts to perform builds. As there is standard build environment and wine, script can compile U++ projects and use them as tools...
The output of the process is implemented as:
- build script or code stores files that is to be uploaded to "~/upload" directory
- then performs ~/bin/upload
Mirek
[Updated on: Wed, 18 March 2009 11:36] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Re: Working on new release system... [message #22254 is a reply to message #20365] |
Sun, 28 June 2009 00:11 |
|
amrein
Messages: 278 Registered: August 2008 Location: France
|
Experienced Member |
|
|
Virtual machines are the easier way to have a complete and good automatic build/test system. Already said this a few months ago.
On Linux or Windows, try http://www.virtualbox.org
Just share a directory in your VMs with read/write access, add needed packages, add a script in your VM to automatically copy and build your new source code from this shared directory and save the binary and logs in this directoy, do a snapshot and then run the VMs with VirtualBox command line tools.
To have up to date Linux release, the script should be able to get updates and then halt the VM before doing a new snapshot with the VirtualBox command line tool (if the script see a "doupdate" file in the shared directory for example).
With multiple VM and with a correct configuration script supporting .upp files configuration, pkg-config and default build directories, all will be automated for good and you will be able to release src, rpm, deb, pkg, exe, 32 bit packages, 64 packages, whatever.
[Updated on: Sun, 28 June 2009 08:53] Report message to a moderator
|
|
|
Goto Forum:
Current Time: Sat Sep 21 02:57:42 CEST 2024
Total time taken to generate the page: 0.06055 seconds
|
|
|