You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Patrick E Laplante <sa...@rochester.rr.com> on 2002/01/03 22:02:32 UTC
Xalan using Code Warrior
I got xalan working on MacOS9 using code warrior.
So you know...
Pat
Re: Xalan using Code Warrior
Posted by Patrick E Laplante <sa...@rochester.rr.com>.
On 03/01/02 16:44, "Manuel Barros" <ma...@enjazz.com> wrote:
First I've looked at the MSDev project to see which file I needed to
include.
Second, I've renamed a bunch of files that were having too long name.
Third, I've created the MacDefinition file that defined compiler options.
Then, I built it and if I remember right, it worked right. I build Xalan
1.2.
In Release mode, I had problem with the compiler so I had to turn off some
option.
> Hi,
>
> I hope this answers your question:
>
> The answer is simple, but probably unsatisfactory. Get the latest Xalan
> distribution, and the latest CodeWarrior compiler, i.e. Version 7.
> Compile the distribution. When you get a set of warnings and compiler
> errors then fix them by either changing the offending lines of code,
> changing compiler options, or changing includes. Repeat this process
> until all the errors are gone. Most of the errors are merely compiler
> and standard template library incompatibilities. The header files in
> the distribution control some of these incompatibilities. The other
> problems are OS related incompatibilities, such as sockets, file
> management, etc. Unfortunately, there is no clear solution to these
> problems, you have to roll your own interface classes for the Mac.
>
> Using this technique, will not only get the project to compile
> eventually, but you will get a chance to learn about the source, which
> you must understand in order to get any use out of Xalan.
>
> You may want to search the net a third party standard template
> library. There is at least one. I can't quite remember the name.
>
> Hope this answers your question. I once got most of the compiler
> errors, but then gave up when I realized how huge the code was, making
> it difficult to keep up with newer distribution releases. This almost a
> year ago.
>
> On Thursday, January 3, 2002, at 04:14 PM, Carlos wrote:
>
>> How did you do it? It¹s more useful to explain the process than to say
>> I did it
>>
>> Thanks
>>
>> Carlos
>>
>> On 01/03/02 13:02, "Patrick E Laplante" <sa...@rochester.rr.com>
>> wrote:
>>
>> I got xalan working on MacOS9 using code warrior.
>> So you know...
>>
>> Pat
>>
>>
>> --
>> Carlos E. Araya
>> ---+ WebCT Administrator/Trainer
>> P | California Virtual Campus
>> - | C/O De Anza College
>> G | 21250 Stevens Creek Blvd
>> ---+ Cupertino, CA 95014
>>
>> email carlos@cvc.edu
>> web http://www.cvc1.org/ (work)
>> http://www.silverwolf-net.net (personal)
>> phone 408 257 0420 (work)
>> PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
>>
>> Paradoxically, a refusal to 'put a monetary value on life' means that
>> life is often undervalued.
>> -- Artificial Intelligence: A Modern Approach
>>
>
Re: Xalan using Code Warrior
Posted by Manuel Barros <ma...@enjazz.com>.
Hi,
I hope this answers your question:
The answer is simple, but probably unsatisfactory. Get the latest Xalan
distribution, and the latest CodeWarrior compiler, i.e. Version 7.
Compile the distribution. When you get a set of warnings and compiler
errors then fix them by either changing the offending lines of code,
changing compiler options, or changing includes. Repeat this process
until all the errors are gone. Most of the errors are merely compiler
and standard template library incompatibilities. The header files in
the distribution control some of these incompatibilities. The other
problems are OS related incompatibilities, such as sockets, file
management, etc. Unfortunately, there is no clear solution to these
problems, you have to roll your own interface classes for the Mac.
Using this technique, will not only get the project to compile
eventually, but you will get a chance to learn about the source, which
you must understand in order to get any use out of Xalan.
You may want to search the net a third party standard template
library. There is at least one. I can't quite remember the name.
Hope this answers your question. I once got most of the compiler
errors, but then gave up when I realized how huge the code was, making
it difficult to keep up with newer distribution releases. This almost a
year ago.
On Thursday, January 3, 2002, at 04:14 PM, Carlos wrote:
> How did you do it? It’s more useful to explain the process than to say
> I did it
>
> Thanks
>
> Carlos
>
> On 01/03/02 13:02, "Patrick E Laplante" <sa...@rochester.rr.com>
> wrote:
>
> I got xalan working on MacOS9 using code warrior.
> So you know...
>
> Pat
>
>
> --
> Carlos E. Araya
> ---+ WebCT Administrator/Trainer
> P | California Virtual Campus
> - | C/O De Anza College
> G | 21250 Stevens Creek Blvd
> ---+ Cupertino, CA 95014
>
> email carlos@cvc.edu
> web http://www.cvc1.org/ (work)
> http://www.silverwolf-net.net (personal)
> phone 408 257 0420 (work)
> PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
>
> Paradoxically, a refusal to 'put a monetary value on life' means that
> life is often undervalued.
> -- Artificial Intelligence: A Modern Approach
>
Re: Xalan using Code Warrior
Posted by Carlos <ca...@cvc.edu>.
How did you do it? It¹s more useful to explain the process than to say I did
it
Thanks
Carlos
On 01/03/02 13:02, "Patrick E Laplante" <sa...@rochester.rr.com> wrote:
> I got xalan working on MacOS9 using code warrior.
> So you know...
>
> Pat
--
Carlos E. Araya
---+ WebCT Administrator/Trainer
P | California Virtual Campus
- | C/O De Anza College
G | 21250 Stevens Creek Blvd
---+ Cupertino, CA 95014
email carlos@cvc.edu
web http://www.cvc1.org/ (work)
http://www.silverwolf-net.net (personal)
phone 408 257 0420 (work)
PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
Paradoxically, a refusal to 'put a monetary value on life' means that life
is often undervalued.
-- Artificial Intelligence: A Modern Approach