Hello.
Yes, the bcc32 is provided by Borland and has Borland options and the bcc64
provided by Embarcadero and it is clang based and has Clang options but
with old linker.
The bcc32c is provided by Embarcadero and it is clang based but has Borland
options wrapper.
Actually I don't interested in Embarcadero itself but in content of files
placed in the .../Modules/Platform folder.
And search some usefully info about the cmake options passed to compiler
and linker.
Also I have tryed to find some info about this files but haven't found
anything about them.
Please share some links or docs if you have.
Thanks.
Valentyn.
On Aug 11, 2017 15:39, "Brad King" <brad.k...@kitware.com> wrote:
> On 08/11/2017 03:18 AM, Валентин Хирный wrote:
> > I've tried to prepare cmake configuration file for Embarcadero bcc64
> compiler.
> > For my practice I chose the name Embarcadero64 for new compiler because
> > bcc64 is clang based compiler.
>
> Does `bcc64` have a radically different command line interface from `bcc32`
> that justifies a separate compiler id? I don't think we have a distinction
> in compiler id based on the target architecture for any other compiler.
>
> Thanks,
> -Brad
>
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers