The Automake and VSExpress build systems have been both removed from TuscanySCA Native with svn revision 592507. WoooHoooo :)
TuscanySCA Native now has a common, unified build system for all platforms: Apache ant. I'll get to work on doing the same for SDO now. -------------------- Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adriano Crestani Sent: Monday, November 05, 2007 10:52 PM To: [email protected] Subject: Re: [Native] VS build versus ant build Thanks for volunteering to get rid of .sh and .bat files brady :D And yes, I will work out on adding ant build to das sample, I expect to have it done till the weekend : ) About the documentation being updated with the new ant build system, I think it's really necessary before the next release, otherwise the docs will be useless, cause there will be no more automake build system :P...maybe Amita can help us with that, she is really good with documentation ; ) Regards, Adriano Crestani On Nov 5, 2007 12:42 PM, Pete Robbins <[EMAIL PROTECTED]> wrote: > On 05/11/2007, Brady Johnson <[EMAIL PROTECTED]> wrote: > > > > I can get started removing all the automake files (this will be fun > > getting rid of automake! :) ). > > > > As for the DAS and SDO samples in ant, the README_ANT_INSTALL > > mentions that the samples are the only item remaining to complete > > the entire ant build system. The samples have been added to ant for > > SCA, Adriano: can you look into completing the samples for DAS? > > > > Do you have some sort of checklist for creating a distribution? If I > > had that, I could get started adding that to the ant build system. > > Not really. The distro was built on linux using "make dist" and on > windows by the builddist.bat scripts. It should be simpler with ant. > For the source distro we just need to zip up the source tree excluding > anything we don't want in the distro (e.g. the PHP extension has never > been build into a release). The binary release needs to include sample > source as well as a zip of the deployed runtime. > > > > > > -------------------- > > Brady Johnson > > Lead Software Developer - HydraSCA > > Rogue Wave Software - [EMAIL PROTECTED] > > > > > > -----Original Message----- > > From: Pete Robbins [mailto:[EMAIL PROTECTED] > > Sent: Monday, November 05, 2007 2:11 AM > > To: [email protected] > > Subject: Re: [Native] VS build versus ant build > > > > I think we should be using ant for everything. The goal is to have a > > command line build and ant will give us that. We need to ensure that > > the samples can also be built/deployed using an ant script and that > > the documentation is updated to reflect this. > > > > While we are at it we should write some ant scripts to build and > > package a distribution. > > > > So, if ant build is working on all platforms we can get rid of the > > VSExpress stuff and the Automake stuff. > > > > Cheers, > > > > On 04/11/2007, Adriano Crestani <[EMAIL PROTECTED]> wrote: > > > There are actually 3 build systems on native projects...make, ant > > > and VSExpress. > > > > > > - Make is completely deprecated with the addition of the new ant > > > build > > > > > process. I think the make build system files (.sh and .bat) could > > > already be removed. > > > > > > - Ant seems to be working for all 3 projects, but DAS and SDO > > > samples > > > > > > - VSExpress seems to be working fine for DAS and SDO, but seems to > > > be broken for SCA(at least the CppCalculator that is the only one > > > I've tested on VSExpress). VSExpress is useful for debugging and > > > development, however it uses .bat files to deploy the generated > > > files, > > > > > adding more files to the maintenance list :s. Is there a way for > > > VSExpress to use ant to deploy its files? This way we would only > > > need to maintain the ant files. Otherwise, here is +1 to remove > > > VSExpress > > files too. > > > > > > Thoughts? Suggestions? > > > > > > Adriano Crestani > > > > > > > > > -- > > Pete > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Pete > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
