RE: [SCA Native] preliminary ant build
I uploaded yet another patch for this JIRA https://issues.apache.org/jira/browse/TUSCANY-1438 Can someone please apply it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 07, 2007 10:52 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I have 2 outstanding patches uploaded for the TuscanySCA Native ant build: - tuscany_patch_update7_jira1438 - tuscany_patch_update8_jira1438 https://issues.apache.org/jira/browse/TUSCANY-1438 Could someone submit them for me please. I had a bit of spare time this weekend, so I'll be uploading the ant build files for TuscanySDO Native soon. I still haven't had a chance to advance the M4 design yet, I hope to be able to start this afternoon. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 9:14 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I added a utility target that displays all of the system properties. Since its in system.xml, it can be executed from any build.xml that imports system.xml, which is pretty much anywhere. Below is a sample output. The svn diff patch is attached. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] [EMAIL PROTECTED] sca]$ ant display.system Buildfile: build.xml check.ws: check.python: check.php: check.ruby: check.rest: display.system: [echo] [echo] TuscanySCA paths [echo] tuscanySDO.install.dir= /nfs/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sdo/deploy [echo] tuscanySCA.root.dir= /amd/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca [echo] tuscanySCA.root.src.dir= /amd/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca/runtime [echo] tuscanySCA.install.dir= /nfs/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca/deploy [echo] tuscanySCA.library.version= '.0.0.0' [echo] [echo] TuscanySCA compiler configuration [echo] compiler.name= 'g++' [echo] lib.ext= '.so' [echo] dll.ext= '' [echo] lib.prefix= 'lib' [echo] object.ext= '.o' [echo] exe.ext= '' [echo] script.ext= '.sh' [echo] [echo] TuscanySCA ws extension enabled [echo] axis2c.home.dir= /nfs/homes/bjohnson/tuscany_cpp/axis2c-src-0.96/deploy [echo] [echo] TuscanySCA php extension enabled [echo] php.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/php-5.1.6/deploy/lib [echo] php.include.dir= /nfs/homes/bjohnson/tuscany_cpp/php-5.1.6/deploy/include/php [echo] php.sca.sdo.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/sdo-1.0.3/lib [echo] php.sca.sdo.include.dir= /nfs/homes/bjohnson/tuscany_cpp/sdo-1.0.3 [echo] [echo] TuscanySCA python extension enabled [echo] python.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/Python-2.5.1/deploy/lib [echo] python.include.dir= /nfs/homes/bjohnson/tuscany_cpp/Python-2.5.1/deploy/include/python2.5 [echo] python.version= python2.5 [echo] [echo] TuscanySCA rest extension enabled [echo] rest.curl.lib.dir=/usr/lib [echo] rest.curl.include.dir=/usr/include/curl [echo] rest.httpd.include.dir= /nfs/homes/bjohnson/tuscany_cpp/httpd-2.0.59/deploy/include [echo] rest.apr.include.dir= /usr/include/apr-0 [echo] [echo] TuscanySCA ruby extension enabled [echo] ruby.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/ruby-1.8.6/deploy/lib [echo] ruby.include.dir= /nfs/homes/bjohnson/tuscany_cpp/ruby-1.8.6/deploy/include [echo] BUILD SUCCESSFUL Total time: 1 second [EMAIL PROTECTED] sca]$ -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 1:13 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build 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
Re: [SCA Native] preliminary ant build
I applied 7 today and will look at 8 now. Cheers On 07/08/07, Brady Johnson [EMAIL PROTECTED] wrote: I have 2 outstanding patches uploaded for the TuscanySCA Native ant build: - tuscany_patch_update7_jira1438 - tuscany_patch_update8_jira1438 https://issues.apache.org/jira/browse/TUSCANY-1438 Could someone submit them for me please. I had a bit of spare time this weekend, so I'll be uploading the ant build files for TuscanySDO Native soon. I still haven't had a chance to advance the M4 design yet, I hope to be able to start this afternoon. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2007 9:14 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I added a utility target that displays all of the system properties. Since its in system.xml, it can be executed from any build.xml that imports system.xml, which is pretty much anywhere. Below is a sample output. The svn diff patch is attached. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] [EMAIL PROTECTED] sca]$ ant display.system Buildfile: build.xml check.ws: check.python: check.php: check.ruby: check.rest: display.system: [echo] [echo] TuscanySCA paths [echo] tuscanySDO.install.dir= /nfs/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sdo/deploy [echo] tuscanySCA.root.dir= /amd/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca [echo] tuscanySCA.root.src.dir= /amd/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca/runtime [echo] tuscanySCA.install.dir= /nfs/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca/deploy [echo] tuscanySCA.library.version= '.0.0.0' [echo] [echo] TuscanySCA compiler configuration [echo] compiler.name= 'g++' [echo] lib.ext= '.so' [echo] dll.ext= '' [echo] lib.prefix= 'lib' [echo] object.ext= '.o' [echo] exe.ext= '' [echo] script.ext= '.sh' [echo] [echo] TuscanySCA ws extension enabled [echo] axis2c.home.dir= /nfs/homes/bjohnson/tuscany_cpp/axis2c-src-0.96/deploy [echo] [echo] TuscanySCA php extension enabled [echo] php.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/php-5.1.6/deploy/lib [echo] php.include.dir= /nfs/homes/bjohnson/tuscany_cpp/php-5.1.6/deploy/include/php [echo] php.sca.sdo.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/sdo-1.0.3/lib [echo] php.sca.sdo.include.dir= /nfs/homes/bjohnson/tuscany_cpp/sdo-1.0.3 [echo] [echo] TuscanySCA python extension enabled [echo] python.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/Python-2.5.1/deploy/lib [echo] python.include.dir= /nfs/homes/bjohnson/tuscany_cpp/Python-2.5.1/deploy/include/python2.5 [echo] python.version= python2.5 [echo] [echo] TuscanySCA rest extension enabled [echo] rest.curl.lib.dir=/usr/lib [echo] rest.curl.include.dir=/usr/include/curl [echo] rest.httpd.include.dir= /nfs/homes/bjohnson/tuscany_cpp/httpd-2.0.59/deploy/include [echo] rest.apr.include.dir= /usr/include/apr-0 [echo] [echo] TuscanySCA ruby extension enabled [echo] ruby.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/ruby-1.8.6/deploy/lib [echo] ruby.include.dir= /nfs/homes/bjohnson/tuscany_cpp/ruby-1.8.6/deploy/include [echo] BUILD SUCCESSFUL Total time: 1 second [EMAIL PROTECTED] sca]$ -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 1:13 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build 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
RE: [SCA Native] preliminary ant build
I added a utility target that displays all of the system properties. Since its in system.xml, it can be executed from any build.xml that imports system.xml, which is pretty much anywhere. Below is a sample output. The svn diff patch is attached. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] [EMAIL PROTECTED] sca]$ ant display.system Buildfile: build.xml check.ws: check.python: check.php: check.ruby: check.rest: display.system: [echo] [echo] TuscanySCA paths [echo] tuscanySDO.install.dir= /nfs/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sdo/deploy [echo] tuscanySCA.root.dir= /amd/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca [echo] tuscanySCA.root.src.dir= /amd/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca/runtime [echo] tuscanySCA.install.dir= /nfs/homes/bjohnson/tuscany_cpp/tuscany_svn_head/sca/deploy [echo] tuscanySCA.library.version= '.0.0.0' [echo] [echo] TuscanySCA compiler configuration [echo] compiler.name= 'g++' [echo] lib.ext= '.so' [echo] dll.ext= '' [echo] lib.prefix= 'lib' [echo] object.ext= '.o' [echo] exe.ext= '' [echo] script.ext= '.sh' [echo] [echo] TuscanySCA ws extension enabled [echo] axis2c.home.dir= /nfs/homes/bjohnson/tuscany_cpp/axis2c-src-0.96/deploy [echo] [echo] TuscanySCA php extension enabled [echo] php.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/php-5.1.6/deploy/lib [echo] php.include.dir= /nfs/homes/bjohnson/tuscany_cpp/php-5.1.6/deploy/include/php [echo] php.sca.sdo.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/sdo-1.0.3/lib [echo] php.sca.sdo.include.dir= /nfs/homes/bjohnson/tuscany_cpp/sdo-1.0.3 [echo] [echo] TuscanySCA python extension enabled [echo] python.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/Python-2.5.1/deploy/lib [echo] python.include.dir= /nfs/homes/bjohnson/tuscany_cpp/Python-2.5.1/deploy/include/python2.5 [echo] python.version= python2.5 [echo] [echo] TuscanySCA rest extension enabled [echo] rest.curl.lib.dir=/usr/lib [echo] rest.curl.include.dir=/usr/include/curl [echo] rest.httpd.include.dir= /nfs/homes/bjohnson/tuscany_cpp/httpd-2.0.59/deploy/include [echo] rest.apr.include.dir= /usr/include/apr-0 [echo] [echo] TuscanySCA ruby extension enabled [echo] ruby.lib.dir= /nfs/homes/bjohnson/tuscany_cpp/ruby-1.8.6/deploy/lib [echo] ruby.include.dir= /nfs/homes/bjohnson/tuscany_cpp/ruby-1.8.6/deploy/include [echo] BUILD SUCCESSFUL Total time: 1 second [EMAIL PROTECTED] sca]$ -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Friday, July 27, 2007 1:13 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build 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
RE: [SCA Native] preliminary ant build
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]
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]
Re: [SCA Native] preliminary ant build
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [SCA Native] preliminary ant build
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]
RE: [SCA Native] preliminary ant build
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]
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]
RE: [SCA Native] preliminary ant build
Pete, I saw the problem with running ant in the top level last night and have it fixed. As for the unresolved references I windows, I have a fix for that that I hope will help. I'm about to test it on windows now. 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]
RE: [SCA Native] preliminary ant build
That was the only drawback that I could see too. Each depot ought to be
basically stand-alone.
As for a top-level build.xml for all 3 projects, that would be very
simple and would not require any of the ant infrastructure used by the
individual projects. It would be very similar to the root build.xml for
TuscanySCA.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 11:30 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
A top level build in tuscany/cpp should be easy to do. I'm not sure we
should move (as Brady suggested) the common ant scripts up into
cpp/etc though. I think it's important that I can extract
tuscany/cpp/sdo, for example, and build it without using anything
outside of that tree.
Cheers,
On 24/07/07, Adriano Crestani [EMAIL PROTECTED] wrote:
Great idea, soon I will try to apply this idea to Native DAS and see
how it
works. I think the idea could also be easily applied to Native SDO, as
it
does not have too much dependencies and code generation as Native SCA
does.
A folder ant-core could be created under tuscany/cpp/ folder to place
the
ant scripts shared by the projects.
Also, we could add a build.xml under tuscany/ccp/ that builds all 3
subprojects at once, if the 3 to implement this ant build process.
What do
you think?
Regards,
Adriano Crestani
On 7/23/07, Brady Johnson [EMAIL PROTECTED] wrote:
Correction, it should be like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}
custom-cc-elements
defineset if=windows define=SCA_EXPORTS/
/custom-cc-elements
/cpp-compile
/target
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 5:05 PM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
Pete,
Good catch. That's an easy fix. I'll submit it with the next patch
tomorrow. Basically it involves removing SCA_EXPORTS from the
Tuscany-BaseCompiler and adding it to the runtime/core/src targets:
compile.core
compile.extension
compile.model
compile.util
Like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}/
custom-cc-element
defineset if=windows define=SCA_EXPORTS/
/custom-cc-element
/target
Tomorrow I'll have the python, ruby, rest, and maybe php extensions
complete.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 2:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I think there is a problem in the extension compilations. The
SCA_EXPORTS directive should only be set when compiling the
runtime/core. When compiling for dlls on windows which use the core
dll
SCA_EXPORTS must not be set. I guess this means we have to move the
setting of this directive from the definition of the
Tuscany-BaseCompiler
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I've applied the patch. How are you creating the patches? I had
trouble applying it on Windows using ToirtoiseSVN.
I've included the changes in the patch to the tools/TuscanyDriver
build. I haven't tested this and I'm not sure if it works with the
system.xml etc.
Can you do a clean extract as a base for future patches?
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'll give this a go. I should be able to run it on Mac as well.
Cheers,
On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I updated the jira1438 with update 3, which includes the
following:
https://issues.apache.org/jira/browse/TUSCANY-1438
- added build.xml for the following dirs:
runtime/extensions/build.xml
runtime/extensions/cpp/build.xml
runtime/extensions/sca/build.xml
runtime/extensions/ws/build.xml
- changed system.xml to check for necessary axis, php, python,
rest, and ruby env vars. If they're not set in the env, look
for
them in platform.properties
- changed compile-targets.xml targets
cpp-install-headers/ to cpp-install-files/
cpp-install-lib/ to cpp-install-file/
- added compile-targets.xml target: cpp-symlink/
- added library versioning and the
platform.tuscanySCA.library.version
Re: [SCA Native] preliminary ant build
I've applied the patch. I'm having a few problems on Windows with my
environment I'm getting errors like:
compile.cpp.osoa:
[cc] 2 total files to be compiled.
[cc] CompositeContext.cpp
[cc]
D:\tuscanysvn\cpp\sca\runtime\extensions\cpp\src\osoa\sca\CompositeContext.cpp(44)
: warning C4273: 'osoa::sca::CompositeContext::CompositeContext' :
inconsistent dll linkage
[cc]
D:\tuscanysvn\cpp\sca\runtime\extensions\cpp\src\osoa/sca/CompositeContext.h(86)
: see previous definition of '{ctor}'
I thought that the SCA_EXPORTS definition was causing this... but maybe not.
The PHP extension is not complete and was not included in the M3
release. What problems are you seeing getting it to build?
Cheers,
On 24/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I updated the jira1438 with update 4, which includes the following:
https://issues.apache.org/jira/browse/TUSCANY-1438
New build.xml files for the following
- runtime/extensions/python
- runtime/extensions/rest
- runtime/extensions/ruby
Moved -DSCA_EXPORT from Tuscany-BaseCompiler in system.xml and added it
to the runtime/core compilations
I'm working on php (which is the only one left for the source code) now,
but its giving me
problems, so it might take a while.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 24, 2007 7:52 AM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
That was the only drawback that I could see too. Each depot ought to be
basically stand-alone.
As for a top-level build.xml for all 3 projects, that would be very
simple and would not require any of the ant infrastructure used by the
individual projects. It would be very similar to the root build.xml for
TuscanySCA.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 11:30 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
A top level build in tuscany/cpp should be easy to do. I'm not sure we
should move (as Brady suggested) the common ant scripts up into
cpp/etc though. I think it's important that I can extract
tuscany/cpp/sdo, for example, and build it without using anything
outside of that tree.
Cheers,
On 24/07/07, Adriano Crestani [EMAIL PROTECTED] wrote:
Great idea, soon I will try to apply this idea to Native DAS and see
how it
works. I think the idea could also be easily applied to Native SDO, as
it
does not have too much dependencies and code generation as Native SCA
does.
A folder ant-core could be created under tuscany/cpp/ folder to place
the
ant scripts shared by the projects.
Also, we could add a build.xml under tuscany/ccp/ that builds all 3
subprojects at once, if the 3 to implement this ant build process.
What do
you think?
Regards,
Adriano Crestani
On 7/23/07, Brady Johnson [EMAIL PROTECTED] wrote:
Correction, it should be like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}
custom-cc-elements
defineset if=windows define=SCA_EXPORTS/
/custom-cc-elements
/cpp-compile
/target
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 5:05 PM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
Pete,
Good catch. That's an easy fix. I'll submit it with the next patch
tomorrow. Basically it involves removing SCA_EXPORTS from the
Tuscany-BaseCompiler and adding it to the runtime/core/src targets:
compile.core
compile.extension
compile.model
compile.util
Like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}/
custom-cc-element
defineset if=windows define=SCA_EXPORTS/
/custom-cc-element
/target
Tomorrow I'll have the python, ruby, rest, and maybe php extensions
complete.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 2:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I think there is a problem in the extension compilations. The
SCA_EXPORTS directive should only be set when compiling the
runtime/core. When compiling for dlls on windows which use the core
dll
SCA_EXPORTS must not be set. I guess
RE: [SCA Native] preliminary ant build
I updated the jira1438 with update 3, which includes the following: https://issues.apache.org/jira/browse/TUSCANY-1438 - added build.xml for the following dirs: runtime/extensions/build.xml runtime/extensions/cpp/build.xml runtime/extensions/sca/build.xml runtime/extensions/ws/build.xml - changed system.xml to check for necessary axis, php, python, rest, and ruby env vars. If they're not set in the env, look for them in platform.properties - changed compile-targets.xml targets cpp-install-headers/ to cpp-install-files/ cpp-install-lib/ to cpp-install-file/ - added compile-targets.xml target: cpp-symlink/ - added library versioning and the platform.tuscanySCA.library.version platform.properties property Can someone submit this for me. The only thing left now is the build.xml for these extensions: php, python, rest, ruby WRT testing on macs, I wont have a mac available until next week. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 8:23 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I can look into testing it on Mac here. I believe we have several mac machines for the purpose. I'll get back to you soon. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef HAVE_STRING_H --- #define HAVE_STRING_H 1 55c56 #undef HAVE_SYS_DIR_H --- /* #undef HAVE_SYS_DIR_H */ 59c60 #undef HAVE_SYS_NDIR_H --- /* #undef HAVE_SYS_NDIR_H */ 62c63 #undef HAVE_SYS_STAT_H --- #define HAVE_SYS_STAT_H 1 65c66 #undef HAVE_SYS_TIME_H --- #define HAVE_SYS_TIME_H 1 68c69 #undef HAVE_SYS_TYPES_H --- #define HAVE_SYS_TYPES_H 1 71c72 #undef HAVE_UNISTD_H --- #define HAVE_UNISTD_H 1 74c75 #undef HAVE_VPRINTF --- #define HAVE_VPRINTF 1 77c78 #undef HAVE__BOOL --- #define HAVE__BOOL 1 80c81 #undef IS_DARWIN --- /* #undef IS_DARWIN */ 84c85 #undef LSTAT_FOLLOWS_SLASHED_SYMLINK --- #define LSTAT_FOLLOWS_SLASHED_SYMLINK 1 87c88 #undef PACKAGE --- #define PACKAGE tuscany_sca_native 90c91 #undef PACKAGE_BUGREPORT --- #define PACKAGE_BUGREPORT 93c94 #undef PACKAGE_NAME --- #define PACKAGE_NAME tuscany_sca_native 96c97 #undef PACKAGE_STRING --- #define PACKAGE_STRING tuscany_sca_native 1.0-incubator-M3 99c100 #undef PACKAGE_TARNAME --- #define PACKAGE_TARNAME tuscany_sca_native 102c103 #undef PACKAGE_VERSION
Re: [SCA Native] preliminary ant build
I'll give this a go. I should be able to run it on Mac as well. Cheers, On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I updated the jira1438 with update 3, which includes the following: https://issues.apache.org/jira/browse/TUSCANY-1438 - added build.xml for the following dirs: runtime/extensions/build.xml runtime/extensions/cpp/build.xml runtime/extensions/sca/build.xml runtime/extensions/ws/build.xml - changed system.xml to check for necessary axis, php, python, rest, and ruby env vars. If they're not set in the env, look for them in platform.properties - changed compile-targets.xml targets cpp-install-headers/ to cpp-install-files/ cpp-install-lib/ to cpp-install-file/ - added compile-targets.xml target: cpp-symlink/ - added library versioning and the platform.tuscanySCA.library.version platform.properties property Can someone submit this for me. The only thing left now is the build.xml for these extensions: php, python, rest, ruby WRT testing on macs, I wont have a mac available until next week. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 8:23 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I can look into testing it on Mac here. I believe we have several mac machines for the purpose. I'll get back to you soon. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef HAVE_STRING_H --- #define HAVE_STRING_H 1 55c56 #undef HAVE_SYS_DIR_H --- /* #undef HAVE_SYS_DIR_H */ 59c60 #undef HAVE_SYS_NDIR_H --- /* #undef HAVE_SYS_NDIR_H */ 62c63 #undef HAVE_SYS_STAT_H --- #define HAVE_SYS_STAT_H 1 65c66 #undef HAVE_SYS_TIME_H --- #define HAVE_SYS_TIME_H 1 68c69 #undef HAVE_SYS_TYPES_H --- #define HAVE_SYS_TYPES_H 1 71c72 #undef HAVE_UNISTD_H --- #define HAVE_UNISTD_H 1 74c75 #undef HAVE_VPRINTF --- #define HAVE_VPRINTF 1 77c78 #undef HAVE__BOOL --- #define HAVE__BOOL 1 80c81 #undef IS_DARWIN --- /* #undef IS_DARWIN */ 84c85 #undef LSTAT_FOLLOWS_SLASHED_SYMLINK --- #define LSTAT_FOLLOWS_SLASHED_SYMLINK 1 87c88 #undef PACKAGE --- #define PACKAGE tuscany_sca_native 90c91 #undef PACKAGE_BUGREPORT --- #define PACKAGE_BUGREPORT 93c94 #undef PACKAGE_NAME --- #define PACKAGE_NAME tuscany_sca_native 96c97 #undef PACKAGE_STRING --- #define PACKAGE_STRING tuscany_sca_native 1.0-incubator-M3 99c100 #undef
Re: [SCA Native] preliminary ant build
Any plans to expand the build to Native SDO and Native DAS ? On 7/23/07, Pete Robbins [EMAIL PROTECTED] wrote: I'll give this a go. I should be able to run it on Mac as well. Cheers, On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I updated the jira1438 with update 3, which includes the following: https://issues.apache.org/jira/browse/TUSCANY-1438 - added build.xml for the following dirs: runtime/extensions/build.xml runtime/extensions/cpp/build.xml runtime/extensions/sca/build.xml runtime/extensions/ws/build.xml - changed system.xml to check for necessary axis, php, python, rest, and ruby env vars. If they're not set in the env, look for them in platform.properties - changed compile-targets.xml targets cpp-install-headers/ to cpp-install-files/ cpp-install-lib/ to cpp-install-file/ - added compile-targets.xml target: cpp-symlink/ - added library versioning and the platform.tuscanySCA.library.version platform.properties property Can someone submit this for me. The only thing left now is the build.xml for these extensions: php, python, rest, ruby WRT testing on macs, I wont have a mac available until next week. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 8:23 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I can look into testing it on Mac here. I believe we have several mac machines for the purpose. I'll get back to you soon. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef HAVE_STRING_H --- #define HAVE_STRING_H 1 55c56 #undef HAVE_SYS_DIR_H --- /* #undef HAVE_SYS_DIR_H */ 59c60 #undef HAVE_SYS_NDIR_H --- /* #undef HAVE_SYS_NDIR_H */ 62c63 #undef HAVE_SYS_STAT_H --- #define HAVE_SYS_STAT_H 1 65c66 #undef HAVE_SYS_TIME_H --- #define HAVE_SYS_TIME_H 1 68c69 #undef HAVE_SYS_TYPES_H --- #define HAVE_SYS_TYPES_H 1 71c72 #undef HAVE_UNISTD_H --- #define HAVE_UNISTD_H 1 74c75 #undef HAVE_VPRINTF --- #define HAVE_VPRINTF 1 77c78 #undef HAVE__BOOL --- #define HAVE__BOOL 1 80c81 #undef IS_DARWIN --- /* #undef IS_DARWIN */ 84c85 #undef LSTAT_FOLLOWS_SLASHED_SYMLINK --- #define LSTAT_FOLLOWS_SLASHED_SYMLINK 1 87c88 #undef PACKAGE --- #define
RE: [SCA Native] preliminary ant build
I had considered doing the same for Native SDO, it shouldn't be so difficult. And why not add das while I'm at it. :) They're both much simpler than sca. It would be nice to be able to share the same core ant build scripts between the 3 products to avoid duplicate code. Is there a way to do that? Im not sure what's in cpp/etc Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Luciano Resende [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 12:20 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build Any plans to expand the build to Native SDO and Native DAS ? On 7/23/07, Pete Robbins [EMAIL PROTECTED] wrote: I'll give this a go. I should be able to run it on Mac as well. Cheers, On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I updated the jira1438 with update 3, which includes the following: https://issues.apache.org/jira/browse/TUSCANY-1438 - added build.xml for the following dirs: runtime/extensions/build.xml runtime/extensions/cpp/build.xml runtime/extensions/sca/build.xml runtime/extensions/ws/build.xml - changed system.xml to check for necessary axis, php, python, rest, and ruby env vars. If they're not set in the env, look for them in platform.properties - changed compile-targets.xml targets cpp-install-headers/ to cpp-install-files/ cpp-install-lib/ to cpp-install-file/ - added compile-targets.xml target: cpp-symlink/ - added library versioning and the platform.tuscanySCA.library.version platform.properties property Can someone submit this for me. The only thing left now is the build.xml for these extensions: php, python, rest, ruby WRT testing on macs, I wont have a mac available until next week. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 8:23 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I can look into testing it on Mac here. I believe we have several mac machines for the purpose. I'll get back to you soon. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef HAVE_STRING_H
Re: [SCA Native] preliminary ant build
I've applied the patch. How are you creating the patches? I had trouble applying it on Windows using ToirtoiseSVN. I've included the changes in the patch to the tools/TuscanyDriver build. I haven't tested this and I'm not sure if it works with the system.xml etc. Can you do a clean extract as a base for future patches? Cheers, On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'll give this a go. I should be able to run it on Mac as well. Cheers, On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I updated the jira1438 with update 3, which includes the following: https://issues.apache.org/jira/browse/TUSCANY-1438 - added build.xml for the following dirs: runtime/extensions/build.xml runtime/extensions/cpp/build.xml runtime/extensions/sca/build.xml runtime/extensions/ws/build.xml - changed system.xml to check for necessary axis, php, python, rest, and ruby env vars. If they're not set in the env, look for them in platform.properties - changed compile-targets.xml targets cpp-install-headers/ to cpp-install-files/ cpp-install-lib/ to cpp-install-file/ - added compile-targets.xml target: cpp-symlink/ - added library versioning and the platform.tuscanySCA.library.version platform.properties property Can someone submit this for me. The only thing left now is the build.xml for these extensions: php, python, rest, ruby WRT testing on macs, I wont have a mac available until next week. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 8:23 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I can look into testing it on Mac here. I believe we have several mac machines for the purpose. I'll get back to you soon. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef HAVE_STRING_H --- #define HAVE_STRING_H 1 55c56 #undef HAVE_SYS_DIR_H --- /* #undef HAVE_SYS_DIR_H */ 59c60 #undef HAVE_SYS_NDIR_H --- /* #undef HAVE_SYS_NDIR_H */ 62c63 #undef HAVE_SYS_STAT_H --- #define HAVE_SYS_STAT_H 1 65c66 #undef HAVE_SYS_TIME_H --- #define HAVE_SYS_TIME_H 1 68c69 #undef HAVE_SYS_TYPES_H --- #define HAVE_SYS_TYPES_H 1 71c72 #undef HAVE_UNISTD_H --- #define HAVE_UNISTD_H 1 74c75 #undef HAVE_VPRINTF --- #define HAVE_VPRINTF 1 77c78
Re: [SCA Native] preliminary ant build
I think there is a problem in the extension compilations. The SCA_EXPORTS directive should only be set when compiling the runtime/core. When compiling for dlls on windows which use the core dll SCA_EXPORTS must not be set. I guess this means we have to move the setting of this directive from the definition of the Tuscany-BaseCompiler Cheers, On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I've applied the patch. How are you creating the patches? I had trouble applying it on Windows using ToirtoiseSVN. I've included the changes in the patch to the tools/TuscanyDriver build. I haven't tested this and I'm not sure if it works with the system.xml etc. Can you do a clean extract as a base for future patches? Cheers, On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'll give this a go. I should be able to run it on Mac as well. Cheers, On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I updated the jira1438 with update 3, which includes the following: https://issues.apache.org/jira/browse/TUSCANY-1438 - added build.xml for the following dirs: runtime/extensions/build.xml runtime/extensions/cpp/build.xml runtime/extensions/sca/build.xml runtime/extensions/ws/build.xml - changed system.xml to check for necessary axis, php, python, rest, and ruby env vars. If they're not set in the env, look for them in platform.properties - changed compile-targets.xml targets cpp-install-headers/ to cpp-install-files/ cpp-install-lib/ to cpp-install-file/ - added compile-targets.xml target: cpp-symlink/ - added library versioning and the platform.tuscanySCA.library.version platform.properties property Can someone submit this for me. The only thing left now is the build.xml for these extensions: php, python, rest, ruby WRT testing on macs, I wont have a mac available until next week. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Brady Johnson [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 8:23 AM To: tuscany-dev@ws.apache.org Subject: RE: [SCA Native] preliminary ant build I can look into testing it on Mac here. I believe we have several mac machines for the purpose. I'll get back to you soon. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef
RE: [SCA Native] preliminary ant build
Pete,
Good catch. That's an easy fix. I'll submit it with the next patch
tomorrow. Basically it involves removing SCA_EXPORTS from the
Tuscany-BaseCompiler and adding it to the runtime/core/src targets:
compile.core
compile.extension
compile.model
compile.util
Like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}/
custom-cc-element
defineset if=windows define=SCA_EXPORTS/
/custom-cc-element
/target
Tomorrow I'll have the python, ruby, rest, and maybe php extensions
complete.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 2:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I think there is a problem in the extension compilations. The
SCA_EXPORTS directive should only be set when compiling the
runtime/core. When compiling for dlls on windows which use the core dll
SCA_EXPORTS must not be set. I guess this means we have to move the
setting of this directive from the definition of the
Tuscany-BaseCompiler
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I've applied the patch. How are you creating the patches? I had
trouble applying it on Windows using ToirtoiseSVN.
I've included the changes in the patch to the tools/TuscanyDriver
build. I haven't tested this and I'm not sure if it works with the
system.xml etc.
Can you do a clean extract as a base for future patches?
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'll give this a go. I should be able to run it on Mac as well.
Cheers,
On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I updated the jira1438 with update 3, which includes the
following:
https://issues.apache.org/jira/browse/TUSCANY-1438
- added build.xml for the following dirs:
runtime/extensions/build.xml
runtime/extensions/cpp/build.xml
runtime/extensions/sca/build.xml
runtime/extensions/ws/build.xml
- changed system.xml to check for necessary axis, php, python,
rest, and ruby env vars. If they're not set in the env, look for
them in platform.properties
- changed compile-targets.xml targets
cpp-install-headers/ to cpp-install-files/
cpp-install-lib/ to cpp-install-file/
- added compile-targets.xml target: cpp-symlink/
- added library versioning and the
platform.tuscanySCA.library.version
platform.properties property
Can someone submit this for me.
The only thing left now is the build.xml for these extensions:
php, python, rest, ruby
WRT testing on macs, I wont have a mac available until next week.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 8:23 AM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
I can look into testing it on Mac here. I believe we have several
mac machines for the purpose.
I'll get back to you soon.
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 2:44 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I've taken out the references to tuscany_sca_config.h and patched
the automake for now with setting -DIS_DARWIN on mac. Yet to test
it on Mac as I need to kick the kids off my machine!
On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
Automake generates a config file with lots of standard stuff but
the only one we need is the IS_DARWIN, which is used in 2
places. I'll remove the 2 references to this header and change
automale to set the IS_DARWIN compile flag.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I did the following diff command and got quite a lot of
changes (listed
below):
# diff tuscany_sca_config.h.in tuscany_sca_config.h
Are these not needed?
If not, I can get to work on removing all references to
the file.
If so, then we still need to figure out how to create
the
file.
I just realized, its 23:30, there... Go to bed! ;)
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
0a1
/* tuscany_sca_config.h. Generated by configure. */
4c5
#undef CLOSEDIR_VOID
---
/* #undef
RE: [SCA Native] preliminary ant build
Correction, it should be like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}
custom-cc-elements
defineset if=windows define=SCA_EXPORTS/
/custom-cc-elements
/cpp-compile
/target
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 5:05 PM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
Pete,
Good catch. That's an easy fix. I'll submit it with the next patch
tomorrow. Basically it involves removing SCA_EXPORTS from the
Tuscany-BaseCompiler and adding it to the runtime/core/src targets:
compile.core
compile.extension
compile.model
compile.util
Like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}/
custom-cc-element
defineset if=windows define=SCA_EXPORTS/
/custom-cc-element
/target
Tomorrow I'll have the python, ruby, rest, and maybe php extensions
complete.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 2:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I think there is a problem in the extension compilations. The
SCA_EXPORTS directive should only be set when compiling the
runtime/core. When compiling for dlls on windows which use the core dll
SCA_EXPORTS must not be set. I guess this means we have to move the
setting of this directive from the definition of the
Tuscany-BaseCompiler
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I've applied the patch. How are you creating the patches? I had
trouble applying it on Windows using ToirtoiseSVN.
I've included the changes in the patch to the tools/TuscanyDriver
build. I haven't tested this and I'm not sure if it works with the
system.xml etc.
Can you do a clean extract as a base for future patches?
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'll give this a go. I should be able to run it on Mac as well.
Cheers,
On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I updated the jira1438 with update 3, which includes the
following:
https://issues.apache.org/jira/browse/TUSCANY-1438
- added build.xml for the following dirs:
runtime/extensions/build.xml
runtime/extensions/cpp/build.xml
runtime/extensions/sca/build.xml
runtime/extensions/ws/build.xml
- changed system.xml to check for necessary axis, php, python,
rest, and ruby env vars. If they're not set in the env, look for
them in platform.properties
- changed compile-targets.xml targets
cpp-install-headers/ to cpp-install-files/
cpp-install-lib/ to cpp-install-file/
- added compile-targets.xml target: cpp-symlink/
- added library versioning and the
platform.tuscanySCA.library.version
platform.properties property
Can someone submit this for me.
The only thing left now is the build.xml for these extensions:
php, python, rest, ruby
WRT testing on macs, I wont have a mac available until next week.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 8:23 AM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
I can look into testing it on Mac here. I believe we have several
mac machines for the purpose.
I'll get back to you soon.
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 2:44 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I've taken out the references to tuscany_sca_config.h and patched
the automake for now with setting -DIS_DARWIN on mac. Yet to test
it on Mac as I need to kick the kids off my machine!
On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
Automake generates a config file with lots of standard stuff but
the only one we need is the IS_DARWIN, which is used in 2
places. I'll remove the 2 references to this header and change
automale to set the IS_DARWIN compile flag.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I did the following diff command and got quite a lot of
changes (listed
below
Re: [SCA Native] preliminary ant build
Great idea, soon I will try to apply this idea to Native DAS and see how it
works. I think the idea could also be easily applied to Native SDO, as it
does not have too much dependencies and code generation as Native SCA does.
A folder ant-core could be created under tuscany/cpp/ folder to place the
ant scripts shared by the projects.
Also, we could add a build.xml under tuscany/ccp/ that builds all 3
subprojects at once, if the 3 to implement this ant build process. What do
you think?
Regards,
Adriano Crestani
On 7/23/07, Brady Johnson [EMAIL PROTECTED] wrote:
Correction, it should be like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}
custom-cc-elements
defineset if=windows define=SCA_EXPORTS/
/custom-cc-elements
/cpp-compile
/target
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 5:05 PM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
Pete,
Good catch. That's an easy fix. I'll submit it with the next patch
tomorrow. Basically it involves removing SCA_EXPORTS from the
Tuscany-BaseCompiler and adding it to the runtime/core/src targets:
compile.core
compile.extension
compile.model
compile.util
Like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}/
custom-cc-element
defineset if=windows define=SCA_EXPORTS/
/custom-cc-element
/target
Tomorrow I'll have the python, ruby, rest, and maybe php extensions
complete.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 2:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I think there is a problem in the extension compilations. The
SCA_EXPORTS directive should only be set when compiling the
runtime/core. When compiling for dlls on windows which use the core dll
SCA_EXPORTS must not be set. I guess this means we have to move the
setting of this directive from the definition of the
Tuscany-BaseCompiler
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I've applied the patch. How are you creating the patches? I had
trouble applying it on Windows using ToirtoiseSVN.
I've included the changes in the patch to the tools/TuscanyDriver
build. I haven't tested this and I'm not sure if it works with the
system.xml etc.
Can you do a clean extract as a base for future patches?
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'll give this a go. I should be able to run it on Mac as well.
Cheers,
On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I updated the jira1438 with update 3, which includes the
following:
https://issues.apache.org/jira/browse/TUSCANY-1438
- added build.xml for the following dirs:
runtime/extensions/build.xml
runtime/extensions/cpp/build.xml
runtime/extensions/sca/build.xml
runtime/extensions/ws/build.xml
- changed system.xml to check for necessary axis, php, python,
rest, and ruby env vars. If they're not set in the env, look for
them in platform.properties
- changed compile-targets.xml targets
cpp-install-headers/ to cpp-install-files/
cpp-install-lib/ to cpp-install-file/
- added compile-targets.xml target: cpp-symlink/
- added library versioning and the
platform.tuscanySCA.library.version
platform.properties property
Can someone submit this for me.
The only thing left now is the build.xml for these extensions:
php, python, rest, ruby
WRT testing on macs, I wont have a mac available until next week.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 8:23 AM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
I can look into testing it on Mac here. I believe we have several
mac machines for the purpose.
I'll get back to you soon.
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 2:44 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I've taken out the references to tuscany_sca_config.h and patched
the automake for now with setting -DIS_DARWIN on mac. Yet
Re: [SCA Native] preliminary ant build
A top level build in tuscany/cpp should be easy to do. I'm not sure we
should move (as Brady suggested) the common ant scripts up into
cpp/etc though. I think it's important that I can extract
tuscany/cpp/sdo, for example, and build it without using anything
outside of that tree.
Cheers,
On 24/07/07, Adriano Crestani [EMAIL PROTECTED] wrote:
Great idea, soon I will try to apply this idea to Native DAS and see how it
works. I think the idea could also be easily applied to Native SDO, as it
does not have too much dependencies and code generation as Native SCA does.
A folder ant-core could be created under tuscany/cpp/ folder to place the
ant scripts shared by the projects.
Also, we could add a build.xml under tuscany/ccp/ that builds all 3
subprojects at once, if the 3 to implement this ant build process. What do
you think?
Regards,
Adriano Crestani
On 7/23/07, Brady Johnson [EMAIL PROTECTED] wrote:
Correction, it should be like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}
custom-cc-elements
defineset if=windows define=SCA_EXPORTS/
/custom-cc-elements
/cpp-compile
/target
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 5:05 PM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
Pete,
Good catch. That's an easy fix. I'll submit it with the next patch
tomorrow. Basically it involves removing SCA_EXPORTS from the
Tuscany-BaseCompiler and adding it to the runtime/core/src targets:
compile.core
compile.extension
compile.model
compile.util
Like this:
target name=compile.core
cpp-compile
srcdir=${core.abs.dir}
objdir=${lib.dir}
infiles=${core.cpp.files}/
custom-cc-element
defineset if=windows define=SCA_EXPORTS/
/custom-cc-element
/target
Tomorrow I'll have the python, ruby, rest, and maybe php extensions
complete.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Monday, July 23, 2007 2:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I think there is a problem in the extension compilations. The
SCA_EXPORTS directive should only be set when compiling the
runtime/core. When compiling for dlls on windows which use the core dll
SCA_EXPORTS must not be set. I guess this means we have to move the
setting of this directive from the definition of the
Tuscany-BaseCompiler
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I've applied the patch. How are you creating the patches? I had
trouble applying it on Windows using ToirtoiseSVN.
I've included the changes in the patch to the tools/TuscanyDriver
build. I haven't tested this and I'm not sure if it works with the
system.xml etc.
Can you do a clean extract as a base for future patches?
Cheers,
On 23/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'll give this a go. I should be able to run it on Mac as well.
Cheers,
On 23/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I updated the jira1438 with update 3, which includes the
following:
https://issues.apache.org/jira/browse/TUSCANY-1438
- added build.xml for the following dirs:
runtime/extensions/build.xml
runtime/extensions/cpp/build.xml
runtime/extensions/sca/build.xml
runtime/extensions/ws/build.xml
- changed system.xml to check for necessary axis, php, python,
rest, and ruby env vars. If they're not set in the env, look for
them in platform.properties
- changed compile-targets.xml targets
cpp-install-headers/ to cpp-install-files/
cpp-install-lib/ to cpp-install-file/
- added compile-targets.xml target: cpp-symlink/
- added library versioning and the
platform.tuscanySCA.library.version
platform.properties property
Can someone submit this for me.
The only thing left now is the build.xml for these extensions:
php, python, rest, ruby
WRT testing on macs, I wont have a mac available until next week.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 19, 2007 8:23 AM
To: tuscany-dev@ws.apache.org
Subject: RE: [SCA Native] preliminary ant build
I can look into testing it on Mac here. I believe we have several
mac machines for the purpose.
I'll get back to you
Re: [SCA Native] preliminary ant build
Automake generates a config file with lots of standard stuff but the
only one we need is the IS_DARWIN, which is used in 2 places. I'll
remove the 2 references to this header and change automale to set the
IS_DARWIN compile flag.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I did the following diff command and got quite a lot of changes (listed
below):
# diff tuscany_sca_config.h.in tuscany_sca_config.h
Are these not needed?
If not, I can get to work on removing all references to the
file.
If so, then we still need to figure out how to create the file.
I just realized, its 23:30, there... Go to bed! ;)
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
0a1
/* tuscany_sca_config.h. Generated by configure. */
4c5
#undef CLOSEDIR_VOID
---
/* #undef CLOSEDIR_VOID */
8c9
#undef HAVE_DIRENT_H
---
#define HAVE_DIRENT_H 1
11c12
#undef HAVE_DLFCN_H
---
#define HAVE_DLFCN_H 1
14c15
#undef HAVE_DOPRNT
---
/* #undef HAVE_DOPRNT */
17c18
#undef HAVE_GETCWD
---
#define HAVE_GETCWD 1
20c21
#undef HAVE_INTTYPES_H
---
#define HAVE_INTTYPES_H 1
23c24
#undef HAVE_MEMORY_H
---
#define HAVE_MEMORY_H 1
26c27
#undef HAVE_NDIR_H
---
/* #undef HAVE_NDIR_H */
29c30
#undef HAVE_PUTENV
---
#define HAVE_PUTENV 1
33c34
#undef HAVE_STAT_EMPTY_STRING_BUG
---
/* #undef HAVE_STAT_EMPTY_STRING_BUG */
36c37
#undef HAVE_STDBOOL_H
---
#define HAVE_STDBOOL_H 1
39c40
#undef HAVE_STDINT_H
---
#define HAVE_STDINT_H 1
42c43
#undef HAVE_STDLIB_H
---
#define HAVE_STDLIB_H 1
45c46
#undef HAVE_STRDUP
---
#define HAVE_STRDUP 1
48c49
#undef HAVE_STRINGS_H
---
#define HAVE_STRINGS_H 1
51c52
#undef HAVE_STRING_H
---
#define HAVE_STRING_H 1
55c56
#undef HAVE_SYS_DIR_H
---
/* #undef HAVE_SYS_DIR_H */
59c60
#undef HAVE_SYS_NDIR_H
---
/* #undef HAVE_SYS_NDIR_H */
62c63
#undef HAVE_SYS_STAT_H
---
#define HAVE_SYS_STAT_H 1
65c66
#undef HAVE_SYS_TIME_H
---
#define HAVE_SYS_TIME_H 1
68c69
#undef HAVE_SYS_TYPES_H
---
#define HAVE_SYS_TYPES_H 1
71c72
#undef HAVE_UNISTD_H
---
#define HAVE_UNISTD_H 1
74c75
#undef HAVE_VPRINTF
---
#define HAVE_VPRINTF 1
77c78
#undef HAVE__BOOL
---
#define HAVE__BOOL 1
80c81
#undef IS_DARWIN
---
/* #undef IS_DARWIN */
84c85
#undef LSTAT_FOLLOWS_SLASHED_SYMLINK
---
#define LSTAT_FOLLOWS_SLASHED_SYMLINK 1
87c88
#undef PACKAGE
---
#define PACKAGE tuscany_sca_native
90c91
#undef PACKAGE_BUGREPORT
---
#define PACKAGE_BUGREPORT
93c94
#undef PACKAGE_NAME
---
#define PACKAGE_NAME tuscany_sca_native
96c97
#undef PACKAGE_STRING
---
#define PACKAGE_STRING tuscany_sca_native 1.0-incubator-M3
99c100
#undef PACKAGE_TARNAME
---
#define PACKAGE_TARNAME tuscany_sca_native
102c103
#undef PACKAGE_VERSION
---
#define PACKAGE_VERSION 1.0-incubator-M3
105c106
#undef STDC_HEADERS
---
#define STDC_HEADERS 1
108c109
#undef VERSION
---
#define VERSION 1.0-incubator-M3
111c112
#undef const
---
/* #undef const */
116c117
#undef inline
---
/* #undef inline */
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 4:22 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
yeah I figured that... I did exactly the same when committing changes
earlier! I dodn't commit the changes inthe tools folder.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Ok, I wasn't aware that I had changed the tools.
I simply did a svn diff . patch_file from the tuscany root dir.
You can disregard the tools changes. I'll look into it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 4:16 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Cool! I've applied this change as well. The update2 patch contained
changes to the tools/TuscanyDriver/build.xml. This doesn't work so you
may want to look at it.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
If that's all we need the tuscany_sca_config.h file for then, yes
this
just got a whole lot easier. We can do the following on the
Tuscany-BaseCompiler
condition property=mac value=true
os family=mac/
/condition
compiler id=Tuscany-BaseCompiler multithreaded=true
exceptions=true rtti=true
defineset if=windows
define=WIN32,_CRT_SECURE_NO_DEPRECATE,SCA_EXPORTS/
defineset if=mac define=IS_DARWIN/
includepath path=${sdo.include.dir}/
includepath path=${tuscanySCA.root.dir}/ !--
tuscany_sca_config.h --
includepath path=${tuscanySCA.root.src.dir}/
includepath path=${tuscanySCA.root.src.dir}/core/src/
/compiler
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto
Re: [SCA Native] preliminary ant build
I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef HAVE_STRING_H --- #define HAVE_STRING_H 1 55c56 #undef HAVE_SYS_DIR_H --- /* #undef HAVE_SYS_DIR_H */ 59c60 #undef HAVE_SYS_NDIR_H --- /* #undef HAVE_SYS_NDIR_H */ 62c63 #undef HAVE_SYS_STAT_H --- #define HAVE_SYS_STAT_H 1 65c66 #undef HAVE_SYS_TIME_H --- #define HAVE_SYS_TIME_H 1 68c69 #undef HAVE_SYS_TYPES_H --- #define HAVE_SYS_TYPES_H 1 71c72 #undef HAVE_UNISTD_H --- #define HAVE_UNISTD_H 1 74c75 #undef HAVE_VPRINTF --- #define HAVE_VPRINTF 1 77c78 #undef HAVE__BOOL --- #define HAVE__BOOL 1 80c81 #undef IS_DARWIN --- /* #undef IS_DARWIN */ 84c85 #undef LSTAT_FOLLOWS_SLASHED_SYMLINK --- #define LSTAT_FOLLOWS_SLASHED_SYMLINK 1 87c88 #undef PACKAGE --- #define PACKAGE tuscany_sca_native 90c91 #undef PACKAGE_BUGREPORT --- #define PACKAGE_BUGREPORT 93c94 #undef PACKAGE_NAME --- #define PACKAGE_NAME tuscany_sca_native 96c97 #undef PACKAGE_STRING --- #define PACKAGE_STRING tuscany_sca_native 1.0-incubator-M3 99c100 #undef PACKAGE_TARNAME --- #define PACKAGE_TARNAME tuscany_sca_native 102c103 #undef PACKAGE_VERSION --- #define PACKAGE_VERSION 1.0-incubator-M3 105c106 #undef STDC_HEADERS --- #define STDC_HEADERS 1 108c109 #undef VERSION --- #define VERSION 1.0-incubator-M3 111c112 #undef const --- /* #undef const */ 116c117 #undef inline --- /* #undef inline */ -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 4:22 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build yeah I figured that... I did exactly the same when committing changes earlier! I dodn't commit the changes inthe tools folder. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Ok, I wasn't aware that I had changed the tools. I simply did a svn diff . patch_file from the tuscany root dir. You can disregard the tools changes. I'll look into it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 4:16 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build Cool! I've applied this change as well. The update2 patch contained changes to the tools/TuscanyDriver/build.xml. This doesn't work so you may want to look at it. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: If that's all we need the tuscany_sca_config.h file for then, yes this just got a whole lot easier. We can do the following on the Tuscany-BaseCompiler condition property=mac value=true os family=mac/ /condition compiler id=Tuscany-BaseCompiler multithreaded=true exceptions=true rtti=true defineset if=windows define=WIN32,_CRT_SECURE_NO_DEPRECATE,SCA_EXPORTS/ defineset
RE: [SCA Native] preliminary ant build
I can look into testing it on Mac here. I believe we have several mac machines for the purpose. I'll get back to you soon. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Thursday, July 19, 2007 2:44 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I've taken out the references to tuscany_sca_config.h and patched the automake for now with setting -DIS_DARWIN on mac. Yet to test it on Mac as I need to kick the kids off my machine! On 19/07/07, Pete Robbins [EMAIL PROTECTED] wrote: Automake generates a config file with lots of standard stuff but the only one we need is the IS_DARWIN, which is used in 2 places. I'll remove the 2 references to this header and change automale to set the IS_DARWIN compile flag. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I did the following diff command and got quite a lot of changes (listed below): # diff tuscany_sca_config.h.in tuscany_sca_config.h Are these not needed? If not, I can get to work on removing all references to the file. If so, then we still need to figure out how to create the file. I just realized, its 23:30, there... Go to bed! ;) Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] 0a1 /* tuscany_sca_config.h. Generated by configure. */ 4c5 #undef CLOSEDIR_VOID --- /* #undef CLOSEDIR_VOID */ 8c9 #undef HAVE_DIRENT_H --- #define HAVE_DIRENT_H 1 11c12 #undef HAVE_DLFCN_H --- #define HAVE_DLFCN_H 1 14c15 #undef HAVE_DOPRNT --- /* #undef HAVE_DOPRNT */ 17c18 #undef HAVE_GETCWD --- #define HAVE_GETCWD 1 20c21 #undef HAVE_INTTYPES_H --- #define HAVE_INTTYPES_H 1 23c24 #undef HAVE_MEMORY_H --- #define HAVE_MEMORY_H 1 26c27 #undef HAVE_NDIR_H --- /* #undef HAVE_NDIR_H */ 29c30 #undef HAVE_PUTENV --- #define HAVE_PUTENV 1 33c34 #undef HAVE_STAT_EMPTY_STRING_BUG --- /* #undef HAVE_STAT_EMPTY_STRING_BUG */ 36c37 #undef HAVE_STDBOOL_H --- #define HAVE_STDBOOL_H 1 39c40 #undef HAVE_STDINT_H --- #define HAVE_STDINT_H 1 42c43 #undef HAVE_STDLIB_H --- #define HAVE_STDLIB_H 1 45c46 #undef HAVE_STRDUP --- #define HAVE_STRDUP 1 48c49 #undef HAVE_STRINGS_H --- #define HAVE_STRINGS_H 1 51c52 #undef HAVE_STRING_H --- #define HAVE_STRING_H 1 55c56 #undef HAVE_SYS_DIR_H --- /* #undef HAVE_SYS_DIR_H */ 59c60 #undef HAVE_SYS_NDIR_H --- /* #undef HAVE_SYS_NDIR_H */ 62c63 #undef HAVE_SYS_STAT_H --- #define HAVE_SYS_STAT_H 1 65c66 #undef HAVE_SYS_TIME_H --- #define HAVE_SYS_TIME_H 1 68c69 #undef HAVE_SYS_TYPES_H --- #define HAVE_SYS_TYPES_H 1 71c72 #undef HAVE_UNISTD_H --- #define HAVE_UNISTD_H 1 74c75 #undef HAVE_VPRINTF --- #define HAVE_VPRINTF 1 77c78 #undef HAVE__BOOL --- #define HAVE__BOOL 1 80c81 #undef IS_DARWIN --- /* #undef IS_DARWIN */ 84c85 #undef LSTAT_FOLLOWS_SLASHED_SYMLINK --- #define LSTAT_FOLLOWS_SLASHED_SYMLINK 1 87c88 #undef PACKAGE --- #define PACKAGE tuscany_sca_native 90c91 #undef PACKAGE_BUGREPORT --- #define PACKAGE_BUGREPORT 93c94 #undef PACKAGE_NAME --- #define PACKAGE_NAME tuscany_sca_native 96c97 #undef PACKAGE_STRING --- #define PACKAGE_STRING tuscany_sca_native 1.0-incubator-M3 99c100 #undef PACKAGE_TARNAME --- #define PACKAGE_TARNAME tuscany_sca_native 102c103 #undef PACKAGE_VERSION --- #define PACKAGE_VERSION 1.0-incubator-M3 105c106 #undef STDC_HEADERS --- #define STDC_HEADERS 1 108c109 #undef VERSION --- #define VERSION 1.0-incubator-M3 111c112 #undef const --- /* #undef const */ 116c117 #undef inline --- /* #undef inline */ -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 4:22 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build yeah I figured that... I did exactly the same when committing changes earlier! I dodn't commit the changes inthe tools folder. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Ok, I wasn't aware that I had changed the tools. I simply did a svn diff . patch_file from the tuscany root dir. You can disregard the tools changes. I'll look into it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 4:16 PM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build Cool! I've applied
Re: [SCA Native] preliminary ant build
I'd like some info on what I need to edit in the platform.properties.
Particularly:
platform.compiler-definition=g++m32
platform=rhas4u4_gcc346
One good thing about automake is that it detects your
platform/compiler etc automatically.
Cheers,
On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in $ANT_HOME/lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in %ANT_HOME%\lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 1:24 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what the
dependencies are (cpptasks etc) and any configuration that is needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that
makes it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release
content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca/runtime/core.
The tar.gz file attached to the jira should just overlay onto the
tuscany SCA cpp source code directory structure. It consists of the
following files:
tuscanySca Native Src dir/
|
| build.xml
|
| antscripts/
| |
| | compilers.xml
| | compile-targets.xml
| | platform.properties
|
| runtime/core/src/build.xml
In order to use it, you will need to modify the platform.properties
file. This will later be taken care of by either configure, or maybe
just an install script.
Currently it compiles and links runtime/core/src/tuscany/sca {core,
extension, model, util} and creates libtuscany_sca.so. The install
target installs the lib and the headers from those src directories to
the install directory specified in platform.properties.
Give it a spin and let me know what you think. It shouldnt take much
to finish it for the rest of tuscany cpp.
If it works out, we can then discuss how to configure
platform.properties.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Re: [SCA Native] preliminary ant build
I ran into a couple of issues tryingt o run this ant build. Firstly I
got an error with a path
x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to
the fact that the property core.dir is set in the top level build.xml
to runtime/core/src and in the runtime/core/src/build.xml the same
property name is used and set tu tuscany/sca/core. It looks to me
like the second defintion of core.dir is being ignored. I'm not an ant
expert ... do properties get propagated from higher level build files?
I got around this by changing the name of core.dir to src.dir in one
of the files.
Rather than specifying the paths to the source code etc in the
platform.properties I would prefer to set these automatically so in
the top level build.xml I added:
property name=tuscanySCA.root.dir location=$env.PWD} /
and then based other properties from this. It seemed to work!
Do these changes make sense?
Cheers,
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'd like some info on what I need to edit in the platform.properties.
Particularly:
platform.compiler-definition=g++m32
platform=rhas4u4_gcc346
One good thing about automake is that it detects your
platform/compiler etc automatically.
Cheers,
On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in $ANT_HOME/lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in %ANT_HOME%\lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 1:24 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what the
dependencies are (cpptasks etc) and any configuration that is needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that
makes it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release
content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca/runtime/core.
The tar.gz file attached to the jira should just overlay onto the
tuscany SCA cpp source code directory structure. It consists of the
following files:
tuscanySca Native Src dir/
|
| build.xml
Re: [SCA Native] preliminary ant build
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I ran into a couple of issues tryingt o run this ant build. Firstly I
got an error with a path
x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to
the fact that the property core.dir is set in the top level build.xml
to runtime/core/src and in the runtime/core/src/build.xml the same
property name is used and set tu tuscany/sca/core. It looks to me
like the second defintion of core.dir is being ignored. I'm not an ant
expert ... do properties get propagated from higher level build files?
I got around this by changing the name of core.dir to src.dir in one
of the files.
Rather than specifying the paths to the source code etc in the
platform.properties I would prefer to set these automatically so in
the top level build.xml I added:
property name=tuscanySCA.root.dir location=$env.PWD} /
or...
property name=tuscanySCA.root.dir location={$basedir} /
and then based other properties from this. It seemed to work!
Do these changes make sense?
Cheers,
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'd like some info on what I need to edit in the platform.properties.
Particularly:
platform.compiler-definition=g++m32
platform=rhas4u4_gcc346
One good thing about automake is that it detects your
platform/compiler etc automatically.
Cheers,
On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in $ANT_HOME/lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in %ANT_HOME%\lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 1:24 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what the
dependencies are (cpptasks etc) and any configuration that is needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that
makes it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release
content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca
Re: [SCA Native] preliminary ant build
Hey Guys
Does a lot of external dependencies need to be setup in order to
proper run the build ? Once this is complete, we could try to
integrate the ant build with Continuun (looks like it supports ant
builds) and try to get a nightly build published for Native project as
well ?
On 7/18/07, Pete Robbins [EMAIL PROTECTED] wrote:
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I ran into a couple of issues tryingt o run this ant build. Firstly I
got an error with a path
x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to
the fact that the property core.dir is set in the top level build.xml
to runtime/core/src and in the runtime/core/src/build.xml the same
property name is used and set tu tuscany/sca/core. It looks to me
like the second defintion of core.dir is being ignored. I'm not an ant
expert ... do properties get propagated from higher level build files?
I got around this by changing the name of core.dir to src.dir in one
of the files.
Rather than specifying the paths to the source code etc in the
platform.properties I would prefer to set these automatically so in
the top level build.xml I added:
property name=tuscanySCA.root.dir location=$env.PWD} /
or...
property name=tuscanySCA.root.dir location={$basedir} /
and then based other properties from this. It seemed to work!
Do these changes make sense?
Cheers,
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'd like some info on what I need to edit in the platform.properties.
Particularly:
platform.compiler-definition=g++m32
platform=rhas4u4_gcc346
One good thing about automake is that it detects your
platform/compiler etc automatically.
Cheers,
On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in $ANT_HOME/lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in %ANT_HOME%\lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 1:24 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what the
dependencies are (cpptasks etc) and any configuration that is needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that
makes it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you
RE: [SCA Native] preliminary ant build
Pete,
Thanks for trying out the ant build scripts.
Regarding core.dir, you're right, the name will need to change. I can do
that no problem.
As for the tuscanySCA.root.dir : Your suggestion will work if you only
execute ant from the root directory, but not if you execute ant from the
runtime/core/src directory. That's why I put it in the
platform.properties, which is accessed by all build.xml's. Its better
ant coding style to have anything that needs to be configured in a
properties file, not in an ant build.xml file.
As for the platform.properties file for windows:
The property platform can/should be removed, its not necessary. If the
property platform.compiler-definition is set, then that value will be
used for the compiler selection, else it will get set to msvc for
windows as can be seen on line 18 of compilers.xml.
I think the way this should ship is to have several platform.properties
files for the different platform:
platform.properties.linux
platform.properties.windows
platform.properties.mac
Which will each have values pre configured for the corresponding
platform. Then with either configure or a shell script, the platform
file wil be copied to platform.properties and the directory properties
will be set accordingly.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 7:08 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I ran into a couple of issues tryingt o run this ant build. Firstly I
got an error with a path
x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to
the fact that the property core.dir is set in the top level build.xml to
runtime/core/src and in the runtime/core/src/build.xml the same
property name is used and set tu tuscany/sca/core. It looks to me like
the second defintion of core.dir is being ignored. I'm not an ant expert
... do properties get propagated from higher level build files?
I got around this by changing the name of core.dir to src.dir in one of
the files.
Rather than specifying the paths to the source code etc in the
platform.properties I would prefer to set these automatically so in the
top level build.xml I added:
property name=tuscanySCA.root.dir location=$env.PWD} /
and then based other properties from this. It seemed to work!
Do these changes make sense?
Cheers,
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'd like some info on what I need to edit in the platform.properties.
Particularly:
platform.compiler-definition=g++m32
platform=rhas4u4_gcc346
One good thing about automake is that it detects your
platform/compiler etc automatically.
Cheers,
On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA
Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be
installed in $ANT_HOME/lib So place the antcontrib and cpptasks jars
there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is
problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be
installed in %ANT_HOME%\lib So place the antcontrib and cpptasks
jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is
problematic
Re: [SCA Native] preliminary ant build
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
Thanks for trying out the ant build scripts.
Regarding core.dir, you're right, the name will need to change. I can do
that no problem.
As for the tuscanySCA.root.dir : Your suggestion will work if you only
execute ant from the root directory, but not if you execute ant from the
runtime/core/src directory. That's why I put it in the
platform.properties, which is accessed by all build.xml's. Its better
ant coding style to have anything that needs to be configured in a
properties file, not in an ant build.xml file.
Yes... I realized that would limit you to running ant from the top
level. So, as most of the info in platform.properties can be deduced
would a better solution be to have a top level (or in antscripts dir)
platform-properties.xml that
a) imports platform.properties for any overrides
b) sets the properties conditional on the platform.
e.g.
condition property=lib.ext value='.so' '
os family='linux'/
/condition
condition property=lib.ext value='.dll' '
os family='windows'/
/condition
condition property=lib.ext value='.dylib '
os family='MacOSX?'/
/condition
As for the platform.properties file for windows:
The property platform can/should be removed, its not necessary. If the
property platform.compiler-definition is set, then that value will be
used for the compiler selection, else it will get set to msvc for
windows as can be seen on line 18 of compilers.xml.
I think the way this should ship is to have several platform.properties
files for the different platform:
platform.properties.linux
platform.properties.windows
platform.properties.mac
Which will each have values pre configured for the corresponding
platform. Then with either configure or a shell script, the platform
file wil be copied to platform.properties and the directory properties
will be set accordingly.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 7:08 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I ran into a couple of issues tryingt o run this ant build. Firstly I
got an error with a path
x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to
the fact that the property core.dir is set in the top level build.xml to
runtime/core/src and in the runtime/core/src/build.xml the same
property name is used and set tu tuscany/sca/core. It looks to me like
the second defintion of core.dir is being ignored. I'm not an ant expert
... do properties get propagated from higher level build files?
I got around this by changing the name of core.dir to src.dir in one of
the files.
Rather than specifying the paths to the source code etc in the
platform.properties I would prefer to set these automatically so in the
top level build.xml I added:
property name=tuscanySCA.root.dir location=$env.PWD} /
and then based other properties from this. It seemed to work!
Do these changes make sense?
Cheers,
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'd like some info on what I need to edit in the platform.properties.
Particularly:
platform.compiler-definition=g++m32
platform=rhas4u4_gcc346
One good thing about automake is that it detects your
platform/compiler etc automatically.
Cheers,
On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA
Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be
installed in $ANT_HOME/lib So place the antcontrib and cpptasks jars
there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is
problematic
Re: [SCA Native] preliminary ant build
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
Thanks for trying out the ant build scripts.
Regarding core.dir, you're right, the name will need to change. I can do
that no problem.
As for the tuscanySCA.root.dir : Your suggestion will work if you only
execute ant from the root directory, but not if you execute ant from the
runtime/core/src directory. That's why I put it in the
platform.properties, which is accessed by all build.xml's. Its better
ant coding style to have anything that needs to be configured in a
properties file, not in an ant build.xml file.
Yes... I realized that would limit you to running ant from the top
level. So, as most of the info in platform.properties can be deduced
would a better solution be to have a top level (or in antscripts dir)
platform-properties.xml that
a) imports platform.properties for any overrides
b) sets the properties conditional on the platform.
e.g.
condition property=lib.ext value='.so' '
os family='linux'/
/condition
condition property=lib.ext value='.dll' '
os family='windows'/
/condition
condition property=lib.ext value='.dylib '
os family='MacOSX?'/
/condition
the build.xml files would all import this top level file:
As for the platform.properties file for windows:
The property platform can/should be removed, its not necessary. If the
property platform.compiler-definition is set, then that value will be
used for the compiler selection, else it will get set to msvc for
windows as can be seen on line 18 of compilers.xml.
I think the way this should ship is to have several platform.properties
files for the different platform:
platform.properties.linux
platform.properties.windows
platform.properties.mac
Which will each have values pre configured for the corresponding
platform. Then with either configure or a shell script, the platform
file wil be copied to platform.properties and the directory properties
will be set accordingly.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 7:08 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
I ran into a couple of issues tryingt o run this ant build. Firstly I
got an error with a path
x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to
the fact that the property core.dir is set in the top level build.xml to
runtime/core/src and in the runtime/core/src/build.xml the same
property name is used and set tu tuscany/sca/core. It looks to me like
the second defintion of core.dir is being ignored. I'm not an ant expert
... do properties get propagated from higher level build files?
I got around this by changing the name of core.dir to src.dir in one of
the files.
Rather than specifying the paths to the source code etc in the
platform.properties I would prefer to set these automatically so in the
top level build.xml I added:
property name=tuscanySCA.root.dir location=$env.PWD} /
and then based other properties from this. It seemed to work!
Do these changes make sense?
Cheers,
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
I'd like some info on what I need to edit in the platform.properties.
Particularly:
platform.compiler-definition=g++m32
platform=rhas4u4_gcc346
One good thing about automake is that it detects your
platform/compiler etc automatically.
Cheers,
On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA
Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be
installed in $ANT_HOME/lib So place the antcontrib
RE: [SCA Native] preliminary ant build
Pete, That's a good idea. Then the only thing that really need to be set in platform.properties file would be: tuscanySCA.install.dir and any possible overides I'll put that together real quick and upload it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, Thanks for trying out the ant build scripts. Regarding core.dir, you're right, the name will need to change. I can do that no problem. As for the tuscanySCA.root.dir : Your suggestion will work if you only execute ant from the root directory, but not if you execute ant from the runtime/core/src directory. That's why I put it in the platform.properties, which is accessed by all build.xml's. Its better ant coding style to have anything that needs to be configured in a properties file, not in an ant build.xml file. Yes... I realized that would limit you to running ant from the top level. So, as most of the info in platform.properties can be deduced would a better solution be to have a top level (or in antscripts dir) platform-properties.xml that a) imports platform.properties for any overrides b) sets the properties conditional on the platform. e.g. condition property=lib.ext value='.so' ' os family='linux'/ /condition condition property=lib.ext value='.dll' ' os family='windows'/ /condition condition property=lib.ext value='.dylib ' os family='MacOSX?'/ /condition the build.xml files would all import this top level file: As for the platform.properties file for windows: The property platform can/should be removed, its not necessary. If the property platform.compiler-definition is set, then that value will be used for the compiler selection, else it will get set to msvc for windows as can be seen on line 18 of compilers.xml. I think the way this should ship is to have several platform.properties files for the different platform: platform.properties.linux platform.properties.windows platform.properties.mac Which will each have values pre configured for the corresponding platform. Then with either configure or a shell script, the platform file wil be copied to platform.properties and the directory properties will be set accordingly. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 7:08 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I ran into a couple of issues tryingt o run this ant build. Firstly I got an error with a path x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to the fact that the property core.dir is set in the top level build.xml to runtime/core/src and in the runtime/core/src/build.xml the same property name is used and set tu tuscany/sca/core. It looks to me like the second defintion of core.dir is being ignored. I'm not an ant expert ... do properties get propagated from higher level build files? I got around this by changing the name of core.dir to src.dir in one of the files. Rather than specifying the paths to the source code etc in the platform.properties I would prefer to set these automatically so in the top level build.xml I added: property name=tuscanySCA.root.dir location=$env.PWD} / and then based other properties from this. It seemed to work! Do these changes make sense? Cheers, On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'd like some info on what I need to edit in the platform.properties. Particularly: platform.compiler-definition=g++m32 platform=rhas4u4_gcc346 One good thing about automake is that it detects your platform/compiler etc automatically. Cheers, On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, I put together some documentation for using ant with TuscanySCA Native. How's this? Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] Using ant to build TuscanySCA Native 1. Required Software to build TuscanySCA Native with ant: Ant: Ant comes installed with almost all Linux distributions version 1.6 or later Download: http://ant.apache.org/ antcontrib: version 1.0b3 or later Download: http://ant
Re: [SCA Native] preliminary ant build
the install dir defaults to sca/deploy so I think we don't need any properties other than overrides. I'll check in what I have. so youi can see. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, That's a good idea. Then the only thing that really need to be set in platform.properties file would be: tuscanySCA.install.dir and any possible overides I'll put that together real quick and upload it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, Thanks for trying out the ant build scripts. Regarding core.dir, you're right, the name will need to change. I can do that no problem. As for the tuscanySCA.root.dir : Your suggestion will work if you only execute ant from the root directory, but not if you execute ant from the runtime/core/src directory. That's why I put it in the platform.properties, which is accessed by all build.xml's. Its better ant coding style to have anything that needs to be configured in a properties file, not in an ant build.xml file. Yes... I realized that would limit you to running ant from the top level. So, as most of the info in platform.properties can be deduced would a better solution be to have a top level (or in antscripts dir) platform-properties.xml that a) imports platform.properties for any overrides b) sets the properties conditional on the platform. e.g. condition property=lib.ext value='.so' ' os family='linux'/ /condition condition property=lib.ext value='.dll' ' os family='windows'/ /condition condition property=lib.ext value='.dylib ' os family='MacOSX?'/ /condition the build.xml files would all import this top level file: As for the platform.properties file for windows: The property platform can/should be removed, its not necessary. If the property platform.compiler-definition is set, then that value will be used for the compiler selection, else it will get set to msvc for windows as can be seen on line 18 of compilers.xml. I think the way this should ship is to have several platform.properties files for the different platform: platform.properties.linux platform.properties.windows platform.properties.mac Which will each have values pre configured for the corresponding platform. Then with either configure or a shell script, the platform file wil be copied to platform.properties and the directory properties will be set accordingly. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 7:08 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I ran into a couple of issues tryingt o run this ant build. Firstly I got an error with a path x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to the fact that the property core.dir is set in the top level build.xml to runtime/core/src and in the runtime/core/src/build.xml the same property name is used and set tu tuscany/sca/core. It looks to me like the second defintion of core.dir is being ignored. I'm not an ant expert ... do properties get propagated from higher level build files? I got around this by changing the name of core.dir to src.dir in one of the files. Rather than specifying the paths to the source code etc in the platform.properties I would prefer to set these automatically so in the top level build.xml I added: property name=tuscanySCA.root.dir location=$env.PWD} / and then based other properties from this. It seemed to work! Do these changes make sense? Cheers, On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'd like some info on what I need to edit in the platform.properties. Particularly: platform.compiler-definition=g++m32 platform=rhas4u4_gcc346 One good thing about automake is that it detects your platform/compiler etc automatically. Cheers, On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, I put together some documentation for using ant with TuscanySCA Native. How's this? Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] Using ant to build TuscanySCA Native 1. Required Software to build TuscanySCA Native with ant: Ant: Ant comes installed with almost all Linux
Re: [SCA Native] preliminary ant build
There is a problem now with this build on a clean system. tuscany-sca-config.h is a header generated by automake that contains directives (IS_DARWIN for example). We will need to have the ant build set compiler options for our conditional compiles instead of this. Cheers, On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: the install dir defaults to sca/deploy so I think we don't need any properties other than overrides. I'll check in what I have. so youi can see. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, That's a good idea. Then the only thing that really need to be set in platform.properties file would be: tuscanySCA.install.dir and any possible overides I'll put that together real quick and upload it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, Thanks for trying out the ant build scripts. Regarding core.dir, you're right, the name will need to change. I can do that no problem. As for the tuscanySCA.root.dir : Your suggestion will work if you only execute ant from the root directory, but not if you execute ant from the runtime/core/src directory. That's why I put it in the platform.properties, which is accessed by all build.xml's. Its better ant coding style to have anything that needs to be configured in a properties file, not in an ant build.xml file. Yes... I realized that would limit you to running ant from the top level. So, as most of the info in platform.properties can be deduced would a better solution be to have a top level (or in antscripts dir) platform-properties.xml that a) imports platform.properties for any overrides b) sets the properties conditional on the platform. e.g. condition property=lib.ext value='.so' ' os family='linux'/ /condition condition property=lib.ext value='.dll' ' os family='windows'/ /condition condition property=lib.ext value='.dylib ' os family='MacOSX?'/ /condition the build.xml files would all import this top level file: As for the platform.properties file for windows: The property platform can/should be removed, its not necessary. If the property platform.compiler-definition is set, then that value will be used for the compiler selection, else it will get set to msvc for windows as can be seen on line 18 of compilers.xml. I think the way this should ship is to have several platform.properties files for the different platform: platform.properties.linux platform.properties.windows platform.properties.mac Which will each have values pre configured for the corresponding platform. Then with either configure or a shell script, the platform file wil be copied to platform.properties and the directory properties will be set accordingly. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 7:08 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I ran into a couple of issues tryingt o run this ant build. Firstly I got an error with a path x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to the fact that the property core.dir is set in the top level build.xml to runtime/core/src and in the runtime/core/src/build.xml the same property name is used and set tu tuscany/sca/core. It looks to me like the second defintion of core.dir is being ignored. I'm not an ant expert ... do properties get propagated from higher level build files? I got around this by changing the name of core.dir to src.dir in one of the files. Rather than specifying the paths to the source code etc in the platform.properties I would prefer to set these automatically so in the top level build.xml I added: property name=tuscanySCA.root.dir location=$env.PWD} / and then based other properties from this. It seemed to work! Do these changes make sense? Cheers, On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: I'd like some info on what I need to edit in the platform.properties. Particularly: platform.compiler-definition=g++m32 platform=rhas4u4_gcc346 One good thing about automake is that it detects your platform/compiler etc automatically. Cheers, On 17/07/07, Brady Johnson [EMAIL PROTECTED] wrote
RE: [SCA Native] preliminary ant build
I uploaded a patch on top of what you submit to svn. Here is a description of what I changed: - Changed the name of compilers.xml to system.xml. - This update has better support for a platform.properties file that is completely empty. That is, all of the platform dependent items are figured out by ant. If they are set in the platform.properties file then they override the ant determination. - Better directory path management has been added to the root build.xml and runtime/core/src/build.xml files. - The install and clean targets in runtime/core/src have been completed. With respect to your latest post regarding tuscany-sca-config.h: I knew this was a problem on clean systems and had envisioned either running a script or using a slimmed down automake/configure to setup this file and any platform specific parameters. That's certainly something we'll have to address, what do you think? Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:22 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build the install dir defaults to sca/deploy so I think we don't need any properties other than overrides. I'll check in what I have. so youi can see. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, That's a good idea. Then the only thing that really need to be set in platform.properties file would be: tuscanySCA.install.dir and any possible overides I'll put that together real quick and upload it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, Thanks for trying out the ant build scripts. Regarding core.dir, you're right, the name will need to change. I can do that no problem. As for the tuscanySCA.root.dir : Your suggestion will work if you only execute ant from the root directory, but not if you execute ant from the runtime/core/src directory. That's why I put it in the platform.properties, which is accessed by all build.xml's. Its better ant coding style to have anything that needs to be configured in a properties file, not in an ant build.xml file. Yes... I realized that would limit you to running ant from the top level. So, as most of the info in platform.properties can be deduced would a better solution be to have a top level (or in antscripts dir) platform-properties.xml that a) imports platform.properties for any overrides b) sets the properties conditional on the platform. e.g. condition property=lib.ext value='.so' ' os family='linux'/ /condition condition property=lib.ext value='.dll' ' os family='windows'/ /condition condition property=lib.ext value='.dylib ' os family='MacOSX?'/ /condition the build.xml files would all import this top level file: As for the platform.properties file for windows: The property platform can/should be removed, its not necessary. If the property platform.compiler-definition is set, then that value will be used for the compiler selection, else it will get set to msvc for windows as can be seen on line 18 of compilers.xml. I think the way this should ship is to have several platform.properties files for the different platform: platform.properties.linux platform.properties.windows platform.properties.mac Which will each have values pre configured for the corresponding platform. Then with either configure or a shell script, the platform file wil be copied to platform.properties and the directory properties will be set accordingly. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 7:08 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build I ran into a couple of issues tryingt o run this ant build. Firstly I got an error with a path x/cpp/sca/runtime/core/src/runtime/core/src. I trcked this down to the fact that the property core.dir is set in the top level build.xml to runtime/core/src and in the runtime/core/src/build.xml the same property name is used and set tu tuscany/sca/core. It looks to me like the second defintion of core.dir is being ignored. I'm
Re: [SCA Native] preliminary ant build
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: I uploaded a patch on top of what you submit to svn. Here is a description of what I changed: - Changed the name of compilers.xml to system.xml. - This update has better support for a platform.properties file that is completely empty. That is, all of the platform dependent items are figured out by ant. If they are set in the platform.properties file then they override the ant determination. - Better directory path management has been added to the root build.xml and runtime/core/src/build.xml files. - The install and clean targets in runtime/core/src have been completed. With respect to your latest post regarding tuscany-sca-config.h: I knew this was a problem on clean systems and had envisioned either running a script or using a slimmed down automake/configure to setup this file and any platform specific parameters. That's certainly something we'll have to address, what do you think? The only reason we use this automake generated file is to set the IS_DARWIN compiler flag for running on Mac OS X. I expect we can use a different technique in ant to set this flag. Is there a family=mac or somesuch in ant? The automake simply runs a 'uname -s' command to figure it out. I think a goal for this shoul be that I can do a clean extract from svn and type ant in the top level directory and it will build with everything defaulted. We need various pre-reqs defined (SDO loccation, + other pre-reqs) but we should try to make this as simple as possible. Cheers, Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:22 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build the install dir defaults to sca/deploy so I think we don't need any properties other than overrides. I'll check in what I have. so youi can see. Cheers, On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, That's a good idea. Then the only thing that really need to be set in platform.properties file would be: tuscanySCA.install.dir and any possible overides I'll put that together real quick and upload it. Thanks Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 18, 2007 9:00 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA Native] preliminary ant build On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote: On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote: Pete, Thanks for trying out the ant build scripts. Regarding core.dir, you're right, the name will need to change. I can do that no problem. As for the tuscanySCA.root.dir : Your suggestion will work if you only execute ant from the root directory, but not if you execute ant from the runtime/core/src directory. That's why I put it in the platform.properties, which is accessed by all build.xml's. Its better ant coding style to have anything that needs to be configured in a properties file, not in an ant build.xml file. Yes... I realized that would limit you to running ant from the top level. So, as most of the info in platform.properties can be deduced would a better solution be to have a top level (or in antscripts dir) platform-properties.xml that a) imports platform.properties for any overrides b) sets the properties conditional on the platform. e.g. condition property=lib.ext value='.so' ' os family='linux'/ /condition condition property=lib.ext value='.dll' ' os family='windows'/ /condition condition property=lib.ext value='.dylib ' os family='MacOSX?'/ /condition the build.xml files would all import this top level file: As for the platform.properties file for windows: The property platform can/should be removed, its not necessary. If the property platform.compiler-definition is set, then that value will be used for the compiler selection, else it will get set to msvc for windows as can be seen on line 18 of compilers.xml. I think the way this should ship is to have several platform.properties files for the different platform: platform.properties.linux platform.properties.windows platform.properties.mac Which will each have values pre configured for the corresponding platform. Then with either configure or a shell script, the platform file wil be copied to platform.properties and the directory properties will be set accordingly. Brady Johnson Lead Software Developer - HydraSCA Rogue Wave Software - [EMAIL PROTECTED] -Original Message- From: Pete Robbins [mailto
RE: [SCA Native] preliminary ant build
If that's all we need the tuscany_sca_config.h file for then, yes this
just got a whole lot easier. We can do the following on the
Tuscany-BaseCompiler
condition property=mac value=true
os family=mac/
/condition
compiler id=Tuscany-BaseCompiler multithreaded=true
exceptions=true rtti=true
defineset if=windows
define=WIN32,_CRT_SECURE_NO_DEPRECATE,SCA_EXPORTS/
defineset if=mac define=IS_DARWIN/
includepath path=${sdo.include.dir}/
includepath path=${tuscanySCA.root.dir}/ !--
tuscany_sca_config.h --
includepath path=${tuscanySCA.root.src.dir}/
includepath path=${tuscanySCA.root.src.dir}/core/src/
/compiler
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 3:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I uploaded a patch on top of what you submit to svn.
Here is a description of what I changed:
- Changed the name of compilers.xml to system.xml.
- This update has better support for a platform.properties file that
is completely empty.
That is, all of the platform dependent items are figured out by ant.
If they are set in
the platform.properties file then they override the ant
determination.
- Better directory path management has been added to the root
build.xml and runtime/core/src/build.xml files.
- The install and clean targets in runtime/core/src have been
completed.
With respect to your latest post regarding tuscany-sca-config.h:
I knew this was a problem on clean systems and had envisioned either
running a script or using a slimmed down automake/configure to setup
this file and any platform specific parameters. That's certainly
something we'll have to address, what do you think?
The only reason we use this automake generated file is to set the
IS_DARWIN compiler flag for running on Mac OS X. I expect we can use a
different technique in ant to set this flag. Is there a family=mac
or somesuch in ant? The automake simply runs a 'uname -s' command to
figure it out.
I think a goal for this shoul be that I can do a clean extract from svn
and type ant in the top level directory and it will build with
everything defaulted. We need various pre-reqs defined (SDO loccation,
+ other pre-reqs) but we should try to make this as simple as
possible.
Cheers,
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:22 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
the install dir defaults to sca/deploy so I think we don't need any
properties other than overrides.
I'll check in what I have. so youi can see.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
That's a good idea. Then the only thing that really need to be set
in platform.properties file would be:
tuscanySCA.install.dir
and any possible overides
I'll put that together real quick and upload it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:00 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
Thanks for trying out the ant build scripts.
Regarding core.dir, you're right, the name will need to change.
I can do that no problem.
As for the tuscanySCA.root.dir : Your suggestion will work if
you only execute ant from the root directory, but not if you
execute ant
from the runtime/core/src directory. That's why I put it in the
platform.properties, which is accessed by all build.xml's. Its
better ant coding style to have anything that needs to be
configured
in a properties file, not in an ant build.xml file.
Yes... I realized that would limit you to running ant from the top
level. So, as most of the info in platform.properties can be
deduced
would a better solution be to have a top level (or in antscripts
dir) platform-properties.xml that
a) imports platform.properties for any overrides
b) sets the properties conditional on the platform.
e.g.
condition property=lib.ext value='.so' '
os family='linux'/
/condition
condition property=lib.ext value='.dll' '
os family='windows'/
/condition
condition property=lib.ext value='.dylib '
os family='MacOSX
Re: [SCA Native] preliminary ant build
Cool! I've applied this change as well. The update2 patch contained
changes to the tools/TuscanyDriver/build.xml. This doesn't work so you
may want to look at it.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
If that's all we need the tuscany_sca_config.h file for then, yes this
just got a whole lot easier. We can do the following on the
Tuscany-BaseCompiler
condition property=mac value=true
os family=mac/
/condition
compiler id=Tuscany-BaseCompiler multithreaded=true
exceptions=true rtti=true
defineset if=windows
define=WIN32,_CRT_SECURE_NO_DEPRECATE,SCA_EXPORTS/
defineset if=mac define=IS_DARWIN/
includepath path=${sdo.include.dir}/
includepath path=${tuscanySCA.root.dir}/ !--
tuscany_sca_config.h --
includepath path=${tuscanySCA.root.src.dir}/
includepath path=${tuscanySCA.root.src.dir}/core/src/
/compiler
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 3:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I uploaded a patch on top of what you submit to svn.
Here is a description of what I changed:
- Changed the name of compilers.xml to system.xml.
- This update has better support for a platform.properties file that
is completely empty.
That is, all of the platform dependent items are figured out by ant.
If they are set in
the platform.properties file then they override the ant
determination.
- Better directory path management has been added to the root
build.xml and runtime/core/src/build.xml files.
- The install and clean targets in runtime/core/src have been
completed.
With respect to your latest post regarding tuscany-sca-config.h:
I knew this was a problem on clean systems and had envisioned either
running a script or using a slimmed down automake/configure to setup
this file and any platform specific parameters. That's certainly
something we'll have to address, what do you think?
The only reason we use this automake generated file is to set the
IS_DARWIN compiler flag for running on Mac OS X. I expect we can use a
different technique in ant to set this flag. Is there a family=mac
or somesuch in ant? The automake simply runs a 'uname -s' command to
figure it out.
I think a goal for this shoul be that I can do a clean extract from svn
and type ant in the top level directory and it will build with
everything defaulted. We need various pre-reqs defined (SDO loccation,
+ other pre-reqs) but we should try to make this as simple as
possible.
Cheers,
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:22 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
the install dir defaults to sca/deploy so I think we don't need any
properties other than overrides.
I'll check in what I have. so youi can see.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
That's a good idea. Then the only thing that really need to be set
in platform.properties file would be:
tuscanySCA.install.dir
and any possible overides
I'll put that together real quick and upload it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:00 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
Thanks for trying out the ant build scripts.
Regarding core.dir, you're right, the name will need to change.
I can do that no problem.
As for the tuscanySCA.root.dir : Your suggestion will work if
you only execute ant from the root directory, but not if you
execute ant
from the runtime/core/src directory. That's why I put it in the
platform.properties, which is accessed by all build.xml's. Its
better ant coding style to have anything that needs to be
configured
in a properties file, not in an ant build.xml file.
Yes... I realized that would limit you to running ant from the top
level. So, as most of the info in platform.properties can be
deduced
would a better solution be to have a top level (or in antscripts
dir) platform-properties.xml that
a) imports platform.properties for any overrides
b) sets the properties conditional on the platform.
e.g.
condition property=lib.ext value='.so' '
os family='linux
RE: [SCA Native] preliminary ant build
Ok, I wasn't aware that I had changed the tools.
I simply did a svn diff . patch_file from the tuscany root dir. You
can disregard the tools changes. I'll look into it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 4:16 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Cool! I've applied this change as well. The update2 patch contained
changes to the tools/TuscanyDriver/build.xml. This doesn't work so you
may want to look at it.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
If that's all we need the tuscany_sca_config.h file for then, yes this
just got a whole lot easier. We can do the following on the
Tuscany-BaseCompiler
condition property=mac value=true
os family=mac/
/condition
compiler id=Tuscany-BaseCompiler multithreaded=true
exceptions=true rtti=true
defineset if=windows
define=WIN32,_CRT_SECURE_NO_DEPRECATE,SCA_EXPORTS/
defineset if=mac define=IS_DARWIN/
includepath path=${sdo.include.dir}/
includepath path=${tuscanySCA.root.dir}/ !--
tuscany_sca_config.h --
includepath path=${tuscanySCA.root.src.dir}/
includepath path=${tuscanySCA.root.src.dir}/core/src/
/compiler
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 3:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I uploaded a patch on top of what you submit to svn.
Here is a description of what I changed:
- Changed the name of compilers.xml to system.xml.
- This update has better support for a platform.properties file that
is completely empty.
That is, all of the platform dependent items are figured out by
ant.
If they are set in
the platform.properties file then they override the ant
determination.
- Better directory path management has been added to the root
build.xml and runtime/core/src/build.xml files.
- The install and clean targets in runtime/core/src have been
completed.
With respect to your latest post regarding tuscany-sca-config.h:
I knew this was a problem on clean systems and had envisioned either
running a script or using a slimmed down automake/configure to setup
this file and any platform specific parameters. That's certainly
something we'll have to address, what do you think?
The only reason we use this automake generated file is to set the
IS_DARWIN compiler flag for running on Mac OS X. I expect we can use a
different technique in ant to set this flag. Is there a family=mac
or somesuch in ant? The automake simply runs a 'uname -s' command to
figure it out.
I think a goal for this shoul be that I can do a clean extract from
svn and type ant in the top level directory and it will build with
everything defaulted. We need various pre-reqs defined (SDO loccation,
+ other pre-reqs) but we should try to make this as simple as
possible.
Cheers,
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:22 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
the install dir defaults to sca/deploy so I think we don't need any
properties other than overrides.
I'll check in what I have. so youi can see.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
That's a good idea. Then the only thing that really need to be set
in platform.properties file would be:
tuscanySCA.install.dir
and any possible overides
I'll put that together real quick and upload it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:00 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
Thanks for trying out the ant build scripts.
Regarding core.dir, you're right, the name will need to
change.
I can do that no problem.
As for the tuscanySCA.root.dir : Your suggestion will work
if you only execute ant from the root directory, but not if
you execute ant
from the runtime/core/src directory. That's why I put it in
the platform.properties, which is accessed
Re: [SCA Native] preliminary ant build
yeah I figured that... I did exactly the same when committing changes
earlier! I dodn't commit the changes inthe tools folder.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Ok, I wasn't aware that I had changed the tools.
I simply did a svn diff . patch_file from the tuscany root dir. You
can disregard the tools changes. I'll look into it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 4:16 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Cool! I've applied this change as well. The update2 patch contained
changes to the tools/TuscanyDriver/build.xml. This doesn't work so you
may want to look at it.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
If that's all we need the tuscany_sca_config.h file for then, yes this
just got a whole lot easier. We can do the following on the
Tuscany-BaseCompiler
condition property=mac value=true
os family=mac/
/condition
compiler id=Tuscany-BaseCompiler multithreaded=true
exceptions=true rtti=true
defineset if=windows
define=WIN32,_CRT_SECURE_NO_DEPRECATE,SCA_EXPORTS/
defineset if=mac define=IS_DARWIN/
includepath path=${sdo.include.dir}/
includepath path=${tuscanySCA.root.dir}/ !--
tuscany_sca_config.h --
includepath path=${tuscanySCA.root.src.dir}/
includepath path=${tuscanySCA.root.src.dir}/core/src/
/compiler
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 3:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I uploaded a patch on top of what you submit to svn.
Here is a description of what I changed:
- Changed the name of compilers.xml to system.xml.
- This update has better support for a platform.properties file that
is completely empty.
That is, all of the platform dependent items are figured out by
ant.
If they are set in
the platform.properties file then they override the ant
determination.
- Better directory path management has been added to the root
build.xml and runtime/core/src/build.xml files.
- The install and clean targets in runtime/core/src have been
completed.
With respect to your latest post regarding tuscany-sca-config.h:
I knew this was a problem on clean systems and had envisioned either
running a script or using a slimmed down automake/configure to setup
this file and any platform specific parameters. That's certainly
something we'll have to address, what do you think?
The only reason we use this automake generated file is to set the
IS_DARWIN compiler flag for running on Mac OS X. I expect we can use a
different technique in ant to set this flag. Is there a family=mac
or somesuch in ant? The automake simply runs a 'uname -s' command to
figure it out.
I think a goal for this shoul be that I can do a clean extract from
svn and type ant in the top level directory and it will build with
everything defaulted. We need various pre-reqs defined (SDO loccation,
+ other pre-reqs) but we should try to make this as simple as
possible.
Cheers,
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:22 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
the install dir defaults to sca/deploy so I think we don't need any
properties other than overrides.
I'll check in what I have. so youi can see.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
That's a good idea. Then the only thing that really need to be set
in platform.properties file would be:
tuscanySCA.install.dir
and any possible overides
I'll put that together real quick and upload it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA Rogue Wave Software -
[EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 9:00 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Pete Robbins [EMAIL PROTECTED] wrote:
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
Thanks for trying out the ant build scripts.
Regarding core.dir, you're right, the name will need to
change.
I can do that no problem.
As for the tuscanySCA.root.dir : Your suggestion will work
if you only execute ant
RE: [SCA Native] preliminary ant build
I did the following diff command and got quite a lot of changes (listed
below):
# diff tuscany_sca_config.h.in tuscany_sca_config.h
Are these not needed?
If not, I can get to work on removing all references to the
file.
If so, then we still need to figure out how to create the file.
I just realized, its 23:30, there... Go to bed! ;)
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
0a1
/* tuscany_sca_config.h. Generated by configure. */
4c5
#undef CLOSEDIR_VOID
---
/* #undef CLOSEDIR_VOID */
8c9
#undef HAVE_DIRENT_H
---
#define HAVE_DIRENT_H 1
11c12
#undef HAVE_DLFCN_H
---
#define HAVE_DLFCN_H 1
14c15
#undef HAVE_DOPRNT
---
/* #undef HAVE_DOPRNT */
17c18
#undef HAVE_GETCWD
---
#define HAVE_GETCWD 1
20c21
#undef HAVE_INTTYPES_H
---
#define HAVE_INTTYPES_H 1
23c24
#undef HAVE_MEMORY_H
---
#define HAVE_MEMORY_H 1
26c27
#undef HAVE_NDIR_H
---
/* #undef HAVE_NDIR_H */
29c30
#undef HAVE_PUTENV
---
#define HAVE_PUTENV 1
33c34
#undef HAVE_STAT_EMPTY_STRING_BUG
---
/* #undef HAVE_STAT_EMPTY_STRING_BUG */
36c37
#undef HAVE_STDBOOL_H
---
#define HAVE_STDBOOL_H 1
39c40
#undef HAVE_STDINT_H
---
#define HAVE_STDINT_H 1
42c43
#undef HAVE_STDLIB_H
---
#define HAVE_STDLIB_H 1
45c46
#undef HAVE_STRDUP
---
#define HAVE_STRDUP 1
48c49
#undef HAVE_STRINGS_H
---
#define HAVE_STRINGS_H 1
51c52
#undef HAVE_STRING_H
---
#define HAVE_STRING_H 1
55c56
#undef HAVE_SYS_DIR_H
---
/* #undef HAVE_SYS_DIR_H */
59c60
#undef HAVE_SYS_NDIR_H
---
/* #undef HAVE_SYS_NDIR_H */
62c63
#undef HAVE_SYS_STAT_H
---
#define HAVE_SYS_STAT_H 1
65c66
#undef HAVE_SYS_TIME_H
---
#define HAVE_SYS_TIME_H 1
68c69
#undef HAVE_SYS_TYPES_H
---
#define HAVE_SYS_TYPES_H 1
71c72
#undef HAVE_UNISTD_H
---
#define HAVE_UNISTD_H 1
74c75
#undef HAVE_VPRINTF
---
#define HAVE_VPRINTF 1
77c78
#undef HAVE__BOOL
---
#define HAVE__BOOL 1
80c81
#undef IS_DARWIN
---
/* #undef IS_DARWIN */
84c85
#undef LSTAT_FOLLOWS_SLASHED_SYMLINK
---
#define LSTAT_FOLLOWS_SLASHED_SYMLINK 1
87c88
#undef PACKAGE
---
#define PACKAGE tuscany_sca_native
90c91
#undef PACKAGE_BUGREPORT
---
#define PACKAGE_BUGREPORT
93c94
#undef PACKAGE_NAME
---
#define PACKAGE_NAME tuscany_sca_native
96c97
#undef PACKAGE_STRING
---
#define PACKAGE_STRING tuscany_sca_native 1.0-incubator-M3
99c100
#undef PACKAGE_TARNAME
---
#define PACKAGE_TARNAME tuscany_sca_native
102c103
#undef PACKAGE_VERSION
---
#define PACKAGE_VERSION 1.0-incubator-M3
105c106
#undef STDC_HEADERS
---
#define STDC_HEADERS 1
108c109
#undef VERSION
---
#define VERSION 1.0-incubator-M3
111c112
#undef const
---
/* #undef const */
116c117
#undef inline
---
/* #undef inline */
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 4:22 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
yeah I figured that... I did exactly the same when committing changes
earlier! I dodn't commit the changes inthe tools folder.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
Ok, I wasn't aware that I had changed the tools.
I simply did a svn diff . patch_file from the tuscany root dir.
You can disregard the tools changes. I'll look into it.
Thanks
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 4:16 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Cool! I've applied this change as well. The update2 patch contained
changes to the tools/TuscanyDriver/build.xml. This doesn't work so you
may want to look at it.
Cheers,
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
If that's all we need the tuscany_sca_config.h file for then, yes
this
just got a whole lot easier. We can do the following on the
Tuscany-BaseCompiler
condition property=mac value=true
os family=mac/
/condition
compiler id=Tuscany-BaseCompiler multithreaded=true
exceptions=true rtti=true
defineset if=windows
define=WIN32,_CRT_SECURE_NO_DEPRECATE,SCA_EXPORTS/
defineset if=mac define=IS_DARWIN/
includepath path=${sdo.include.dir}/
includepath path=${tuscanySCA.root.dir}/ !--
tuscany_sca_config.h --
includepath path=${tuscanySCA.root.src.dir}/
includepath path=${tuscanySCA.root.src.dir}/core/src/
/compiler
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 3:41 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
On 18/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
I uploaded a patch on top of what you submit to svn.
Here is a description
Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what
the dependencies are (cpptasks etc) and any configuration that is
needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that makes
it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca/runtime/core.
The tar.gz file attached to the jira should just overlay onto the
tuscany SCA cpp source code directory structure. It consists of the
following files:
tuscanySca Native Src dir/
|
| build.xml
|
| antscripts/
| |
| | compilers.xml
| | compile-targets.xml
| | platform.properties
|
| runtime/core/src/build.xml
In order to use it, you will need to modify the platform.properties
file. This will later be taken care of by either configure, or maybe
just an install script.
Currently it compiles and links runtime/core/src/tuscany/sca {core,
extension, model, util} and creates libtuscany_sca.so. The install
target installs the lib and the headers from those src directories to
the install directory specified in platform.properties.
Give it a spin and let me know what you think. It shouldnt take much to
finish it for the rest of tuscany cpp.
If it works out, we can then discuss how to configure
platform.properties.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[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]
RE: [SCA Native] preliminary ant build
Pete,
I put together some documentation for using ant with TuscanySCA Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in $ANT_HOME/lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in %ANT_HOME%\lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 1:24 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what the
dependencies are (cpptasks etc) and any configuration that is needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that
makes it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release
content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca/runtime/core.
The tar.gz file attached to the jira should just overlay onto the
tuscany SCA cpp source code directory structure. It consists of the
following files:
tuscanySca Native Src dir/
|
| build.xml
|
| antscripts/
| |
| | compilers.xml
| | compile-targets.xml
| | platform.properties
|
| runtime/core/src/build.xml
In order to use it, you will need to modify the platform.properties
file. This will later be taken care of by either configure, or maybe
just an install script.
Currently it compiles and links runtime/core/src/tuscany/sca {core,
extension, model, util} and creates libtuscany_sca.so. The install
target installs the lib and the headers from those src directories to
the install directory specified in platform.properties.
Give it a spin and let me know what you think. It shouldnt take much
to finish it for the rest of tuscany cpp.
If it works out, we can then discuss how to configure
platform.properties.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[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
Re: [SCA Native] preliminary ant build
Should this documentation go under
http://incubator.apache.org/tuscany/sca-native-developer-guide.html
I can move it if yes.
On 7/17/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in $ANT_HOME/lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in %ANT_HOME%\lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 1:24 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what the
dependencies are (cpptasks etc) and any configuration that is needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that
makes it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release
content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca/runtime/core.
The tar.gz file attached to the jira should just overlay onto the
tuscany SCA cpp source code directory structure. It consists of the
following files:
tuscanySca Native Src dir/
|
| build.xml
|
| antscripts/
| |
| | compilers.xml
| | compile-targets.xml
| | platform.properties
|
| runtime/core/src/build.xml
In order to use it, you will need to modify the platform.properties
file. This will later be taken care of by either configure, or maybe
just an install script.
Currently it compiles and links runtime/core/src/tuscany/sca {core,
extension, model, util} and creates libtuscany_sca.so. The install
target installs the lib and the headers from those src directories to
the install directory specified in platform.properties.
Give it a spin and let me know what you think. It shouldnt take much
to finish it for the rest of tuscany cpp.
If it works out, we can then discuss how to configure
platform.properties.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Pete
Re: [SCA Native] preliminary ant build
On 17/07/07, haleh mahbod [EMAIL PROTECTED] wrote:
Should this documentation go under
http://incubator.apache.org/tuscany/sca-native-developer-guide.html
I can move it if yes.
I think we should wait until we move over to an ant build... which
will take a little longer.
Cheers,
On 7/17/07, Brady Johnson [EMAIL PROTECTED] wrote:
Pete,
I put together some documentation for using ant with TuscanySCA Native.
How's this?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
Using ant to build TuscanySCA Native
1. Required Software to build TuscanySCA Native with ant:
Ant:
Ant comes installed with almost all Linux distributions
version 1.6 or later
Download: http://ant.apache.org/
antcontrib:
version 1.0b3 or later
Download: http://ant-contrib.sourceforge.net/
antcontrib cpptasks.jar
version 1.0b4 or later
Download: http://ant-contrib.sourceforge.net/
Information: http://ant-contrib.sourceforge.net/cc.html
2. Installation Instructions:
Linux
-
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
export ANT_HOME=/home/you/ant
Add $ANT_HOME/bin to your path.
export PATH=${PATH}:${ANT_HOME}/bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in $ANT_HOME/lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to $ANT_HOME/lib, do the following:
- create ${user.home}/.ant/lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
Windows
---
Make sure JAVA_HOME is set before starting.
Install ant according to http://ant.apache.org/manual/index.html.
Set the ANT_HOME variable to the directory where you install ant.
set ANT_HOME=c:\ant
Add %ANT_HOME%\bin to your path.
set PATH=%PATH%;%ANT_HOME%\bin
Optional ant tasks, such as antcontrib and cpptasks, should be installed
in %ANT_HOME%\lib
So place the antcontrib and cpptasks jars there.
If you dont have write access to %ANT_HOME%\lib, do the following:
- create ${user.home}\.ant\lib
- place the jars here
Avoid adding optional ant tasks to your classpath, this is problematic.
-Original Message-
From: Pete Robbins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 17, 2007 1:24 AM
To: tuscany-dev@ws.apache.org
Subject: Re: [SCA Native] preliminary ant build
Thanks Brady. I'll take a look at this. We will need doc as to what the
dependencies are (cpptasks etc) and any configuration that is needed.
Cheers,
On 16/07/07, Brady Johnson [EMAIL PROTECTED] wrote:
For anyone interested, I uploaded another patch for this JIRA that
makes it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release
content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca/runtime/core.
The tar.gz file attached to the jira should just overlay onto the
tuscany SCA cpp source code directory structure. It consists of the
following files:
tuscanySca Native Src dir/
|
| build.xml
|
| antscripts/
| |
| | compilers.xml
| | compile-targets.xml
| | platform.properties
|
| runtime/core/src/build.xml
In order to use it, you will need to modify the platform.properties
file. This will later be taken care of by either configure, or maybe
just an install script.
Currently it compiles and links runtime/core/src/tuscany/sca {core,
extension, model, util} and creates libtuscany_sca.so. The install
target installs the lib and the headers from those src directories to
the install directory specified in platform.properties.
Give it a spin and let me know what you think. It shouldnt take much
to finish it for the rest of tuscany cpp.
If it works out, we can then discuss how to configure
platform.properties.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave
RE: [SCA Native] preliminary ant build
For anyone interested, I uploaded another patch for this JIRA that makes
it work better for windows.
tuscanySCAnative_ant_update1.tar.gz
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-Original Message-
From: Brady Johnson [mailto:[EMAIL PROTECTED]
Sent: Monday, July 16, 2007 10:46 AM
To: tuscany-dev@ws.apache.org
Subject: [SCA Native] preliminary ant build
Hello,
This may be the second time you receive this email, the first time I
sent it with an attachment, which I later realized that this dist list
may reject. So here it is again, w/o the attachment. I created a JIRA
and put the attachment there:
https://issues.apache.org/jira/browse/TUSCANY-1438
According to a previous thread titled [SCA Native] next release content
[was: Tuscany roadmap] (I didnt want to add another was redirection
;) ), I have prepared ant build scripts for cpp/sca/runtime/core.
The tar.gz file attached to the jira should just overlay onto the
tuscany SCA cpp source code directory structure. It consists of the
following files:
tuscanySca Native Src dir/
|
| build.xml
|
| antscripts/
| |
| | compilers.xml
| | compile-targets.xml
| | platform.properties
|
| runtime/core/src/build.xml
In order to use it, you will need to modify the platform.properties
file. This will later be taken care of by either configure, or maybe
just an install script.
Currently it compiles and links runtime/core/src/tuscany/sca {core,
extension, model, util} and creates libtuscany_sca.so. The install
target installs the lib and the headers from those src directories to
the install directory specified in platform.properties.
Give it a spin and let me know what you think. It shouldnt take much to
finish it for the rest of tuscany cpp.
If it works out, we can then discuss how to configure
platform.properties.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
