and now I've moved the core schema to cpp/sca/runtime/core/xsd On 27/07/07, Pete Robbins <[EMAIL PROTECTED]> wrote: > OK.. done! runtime/core/build.xml replaces runtime/core/src/build.xml > > I'll move the xsd dir later. > > Cheers, > > On 27/07/07, Brady Johnson <[EMAIL PROTECTED]> wrote: > > > > Your changes sound good. When you move the build.xml up to > > tuscany/cpp/sca/runtime/core, you'll have to change the path properties > > and the basedir of the root <project/> element. > > > > -------------------- > > Brady Johnson > > Lead Software Developer - HydraSCA > > Rogue Wave Software - [EMAIL PROTECTED] > > > > > > -----Original Message----- > > From: Pete Robbins [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 27, 2007 3:15 AM > > To: tuscany-dev@ws.apache.org > > Subject: Re: [SCA Native] preliminary ant build > > > > I've applied the latest patch and it looks good. I have added install > > and clean targets for the xsd schema that get deployed. > > > > I think the schema that are currently in tuscany/cpp/sca/xsd should be > > moved to tuscany/cpp/sca/runtime/core/xsd which would be a more logical > > place for them. I would also like to move the build.xml file from > > tuscany/cpp/sca/runtime/core/src up one level to > > tuscany/cpp/sca/runtime/core. > > > > What do you think? > > > > Cheers, > > > > On 26/07/07, Brady Johnson <[EMAIL PROTECTED]> wrote: > > > > > > I updated yet another patch which includes the following changes: > > > > > > - compile_targets.xml added <cpp-install-lib/> which calls > > > <cpp-install-file/>. > > > This fixes the case for windows where *.lib needs to go in lib/ and > > > *.dll in bin/ > > > - system.xml added targets: > > > <check.ws/>, <check.php/>, <check.python/>, <check.rest/>, > > > <check.ruby/> These are called by the extension compile, link, and > > > install targets to check if the respective extensions have been > > > enabled. > > > - Added export definitions for Windows extension compilations. > > > - Added dependant libraries to extension link targets. > > > > > > > > > I think this should pretty much cover everything except the samples. > > > > > > > > > -------------------- > > > Brady Johnson > > > Lead Software Developer - HydraSCA > > > Rogue Wave Software - [EMAIL PROTECTED] > > > > > > > > > > > > -----Original Message----- > > > From: Pete Robbins [mailto:[EMAIL PROTECTED] > > > Sent: Thursday, July 26, 2007 12:44 AM > > > To: tuscany-dev@ws.apache.org > > > Subject: Re: [SCA Native] preliminary ant build > > > > > > More good stuff. I've applied the latest patch but there are some > > > issues. > > > > > > From a clean build if you just type "ant" in the top level cpp/sca > > > directory then the build will fail on tuscany_sca_cpp because it needs > > > > > to link against <deploy_dir>/lib/tuscany_sca.dll which has not yet > > > been installed as all the "build" targets are run recursively before > > > the "install" targets. > > > > > > I also get a lot of unresolved references on windows when linking the > > > tuscany_sca_cpp which I will look into. > > > > > > Cheers, > > > > > > On 25/07/07, Brady Johnson <[EMAIL PROTECTED]> wrote: > > > > > > > > I just uploaded patch update 5 which includes the following: > > > > > > > > - runtime/extensions/php/build.xml > > > > - minor change to php code so that it compiles > > > > - compile-targets.xml added cpp-link-core which does not link in the > > > > > > tuscany_sca lib and changed cpp-link so that it does link it in. > > > > > > > > I'm working on the windows exports for the extensions, but windows > > > > isn't behaving for me right now. (I really do dislike working with > > > > microsoft) Hopefully I'll have this done soon. > > > > > > > > -------------------- > > > > Brady Johnson > > > > Lead Software Developer - HydraSCA > > > > Rogue Wave Software - [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] > > > > > > > > > > > > -- > > 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 >
-- Pete --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
