----- Original Message ----
From: Gevorg Voskanyan <v_gevorg@yahoo.com>
Actually it says use spaces instead of tabs and use tabs of 4... This line saves me lots of headache all over the code.
Yes, but still there are tab characters physically in the file, and Boost.Inspect will not like that.
Ok, I'll check, I may missed some.
As a Boost.Build user I would see it very beneficial when using Boost.Locale
to
be able to have ICU build from source with BB just like the other 3rd party
libraries commonly are. For it to work Boost.Locale Jamfile can check if
a
project /icu is available, and if so use /icu//icu as source and skip ICU
configuration checking together with options for linking to prebuilt ICU. I can prepare and propose a patch for this if that scheme is OK with you.
By no means.
Why? It would take only about 5 lines of code to support that.
What do you mean? To start native ICU build?
ICU is very-very complex library that has its own autotools based build system that by no means can be easily (if at all) ported to BBv2.
Perhaps not easily, but I'm sure it's doable.
If somebody like Vladimir Prus does it it may be doable but not with current state of BB documentation.
I have enough bad times with BB building a relatively simple library Boost.Locale...
I was not suggesting for *you* to port ICU to BB, of course not. I understand
it's not a trivial task, and I remember well the struggle you went through to
have Boost.Locale to build with BB. BTW, thanks for not giving up in the middle!
Your persistence with bringing Boost.Locale to where it is now benefited the community. And it would not be polite, to put it mildly, had someone asked you
to do that porting.
So what is the problem for Boost.Locale to accommodate to a user who has ICU ported to BBv2 for his needs?
If someone ports it would be very good. In any case there are rumors in ICU mailing lists on the fact that it may move to CMake which would make it much easier to integrate it with probably the next version of Boost's build system. Best, Artyom