RE: [DAS Native] ant build
Adriano,
I'll try to look into this tomorrow. In the meantime, there is a file
generated in the destination directory (where the object files and/or
library is written) by ant called history.xml. If you look at the
signature attribute of the processor/ element you can see the compiler
command line generated by ant. Hopefully this will help out.
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Adriano Crestani
Sent: Sunday, September 02, 2007 1:36 PM
To: tuscany-dev@ws.apache.org
Subject: Re: [DAS Native] ant build
Back from vacation, back to work : )
Brady, I thought the error had something to do with the pc I was using
while
my laptop was getting repaired, but I got it repaired and the error was
still occurring on my laptop. The error seems rationed to the sdo ant
build,
cause I ignored the DAS ant build and built it like I was building
before,
with the MVS, but got the same error :S. Than I rebuilt the SDO, but not
using the new sdo build, but the old one, the build.bat, and guess what,
there was no more error : ).
It is not exactly an error, when I build the SDO using the ant build, my
DAS
requires the dll MSVCP80.dll and with the old SDO build it does not.
There
may be some option that is being set on SDO ant build that is not on SDO
old
build. I'm not a C++ expert, but I think it has something to do with the
option Multi-threaded Debug DLL (/MDd) or Multi-threaded Debug (/MTd) on
compiler arguments.
Another point, the sdo_test is also requiring this dll when built using
the
SDO ant build (I built the SDO using ant build and compiled the sdo_test
on
MVS, but I removed the sdo_test dependency from sdo_runtime, otherwise
it
would get compiled overwriting the SDO ant build binaries on deploy
folder).
Doing another tests right now to check whether it is a Multi-threaded
Debug
DLL (/MDd) or Multi-threaded Debug (/MTd) problem.
Regards,
Adriano Crestani
On 8/16/07, Adriano Crestani [EMAIL PROTECTED] wrote:
Hi Brady,
Yes, I was plaining to do that after this weekend. I had no chance to
do
that so far, cause I was really busy with college's stuffs :(
Regards,
Adriano Crestani
On 8/16/07, Brady Johnson [EMAIL PROTECTED] wrote:
Adriano,
You might have seen that both SCA and SDO native now have an ant
build
infrastructure. I briefly looked at doing the same for DAS, but
couldn't
get it to compile with configure, make, make install at the time,
and
never got a chance to come back to it.
I think it should be very easy to copy the SDO ant stuff over to
DAS,
what do you think?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
Behalf Of Adriano Crestani
Sent: Monday, July 23, 2007 11:21 PM
To: tuscany-dev@ws.apache.org
Subject: 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
Re: [DAS Native] ant build
Back from vacation, back to work : )
Brady, I thought the error had something to do with the pc I was using while
my laptop was getting repaired, but I got it repaired and the error was
still occurring on my laptop. The error seems rationed to the sdo ant build,
cause I ignored the DAS ant build and built it like I was building before,
with the MVS, but got the same error :S. Than I rebuilt the SDO, but not
using the new sdo build, but the old one, the build.bat, and guess what,
there was no more error : ).
It is not exactly an error, when I build the SDO using the ant build, my DAS
requires the dll MSVCP80.dll and with the old SDO build it does not. There
may be some option that is being set on SDO ant build that is not on SDO old
build. I'm not a C++ expert, but I think it has something to do with the
option Multi-threaded Debug DLL (/MDd) or Multi-threaded Debug (/MTd) on
compiler arguments.
Another point, the sdo_test is also requiring this dll when built using the
SDO ant build (I built the SDO using ant build and compiled the sdo_test on
MVS, but I removed the sdo_test dependency from sdo_runtime, otherwise it
would get compiled overwriting the SDO ant build binaries on deploy folder).
Doing another tests right now to check whether it is a Multi-threaded Debug
DLL (/MDd) or Multi-threaded Debug (/MTd) problem.
Regards,
Adriano Crestani
On 8/16/07, Adriano Crestani [EMAIL PROTECTED] wrote:
Hi Brady,
Yes, I was plaining to do that after this weekend. I had no chance to do
that so far, cause I was really busy with college's stuffs :(
Regards,
Adriano Crestani
On 8/16/07, Brady Johnson [EMAIL PROTECTED] wrote:
Adriano,
You might have seen that both SCA and SDO native now have an ant build
infrastructure. I briefly looked at doing the same for DAS, but couldn't
get it to compile with configure, make, make install at the time, and
never got a chance to come back to it.
I think it should be very easy to copy the SDO ant stuff over to DAS,
what do you think?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Adriano Crestani
Sent: Monday, July 23, 2007 11:21 PM
To: tuscany-dev@ws.apache.org
Subject: 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
[DAS Native] ant build
Adriano,
You might have seen that both SCA and SDO native now have an ant build
infrastructure. I briefly looked at doing the same for DAS, but couldn't
get it to compile with configure, make, make install at the time, and
never got a chance to come back to it.
I think it should be very easy to copy the SDO ant stuff over to DAS,
what do you think?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Adriano Crestani
Sent: Monday, July 23, 2007 11:21 PM
To: tuscany-dev@ws.apache.org
Subject: 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]
Re: [DAS Native] ant build
Hi Brady,
Yes, I was plaining to do that after this weekend. I had no chance to do
that so far, cause I was really busy with college's stuffs :(
Regards,
Adriano Crestani
On 8/16/07, Brady Johnson [EMAIL PROTECTED] wrote:
Adriano,
You might have seen that both SCA and SDO native now have an ant build
infrastructure. I briefly looked at doing the same for DAS, but couldn't
get it to compile with configure, make, make install at the time, and
never got a chance to come back to it.
I think it should be very easy to copy the SDO ant stuff over to DAS,
what do you think?
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Adriano Crestani
Sent: Monday, July 23, 2007 11:21 PM
To: tuscany-dev@ws.apache.org
Subject: 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
