Kylix support

From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-01-15 06:25:00

Felix E. Klee wrote:
> On Friday 10 January 2003 03:50 pm, Vladimir Prus wrote:
>
>>>AFAIK Kylix BCB is pretty similar to BCB 6 for Windows (don't have
>>>experience with that Windows version, though). So, "translating" your
>>>Borland toolset from Windows to LINUX probably isn't that hard. If you
>>>could send it to me, then I can try it out. I'm still a newbie to Boost,
>>>hower, so don't expect to much.
>>
>>Great. The borland toolset is in CVS already. You can go to
>>examples-v2/hello directory again, change "gcc" to "borland" in
>>projet-root.jam, and then type "bjam borland". The build will fail, but you
>>can then go to
>>tools/build/new/borland.jam, browse though it and try to adjust the command
>>lines.
>
>
> Ok, I just did it (see attachment). It really wasn't much work, I only had to
> replace borland by kylix, bcc32 by bc++, and tlib by ar. However, there might
> still be some finetuning neccessary due to several bugs in Kylix. Also I
> haven't added support for shared libraries yet. Maybe I'll try out Boost
> Build V2 with Kylix on a project later this week. This might force me to add
> more features to kylix.jam.

Thanks a lot. I think that mechanisms for inheriting toolset definitions are 
becoming urgently needed -- so that we don't duplicate lot of code.

I'm not yet successfull installing Kylix, so I can't test your changes yet, 
but we'll integrate them asap anyway.

BTW, how shared libraries work on Kylix? In the same was as for ordinary 
Linux/gcc?

Thanks,
Volodya