Compiler: Some compiler flags incompatible between CGT and GCC

Bartlomiej Kucharczyk

Tool/software: TI C/C++ Compiler

Hello,

Let's assume a common library for multiple architectures: arm (GCC) and c6x (CGT). Maintainers of the library would like to provide a pkg-config file (pkg-config -- tool to get compile/link flags). pkg-config tool is designed to work natively with gcc-like flags [1]. Unfortunately due to incompatibility between GCC and CGT [2], it is not possible to provide uniform pkg-config file for both architectures, because neither pkg-config will properly return flags, nor other systems that depend on pkg-config behavior (for example cmake-based build systems).

What is your proposed way to solve this incompatibility?

With regards,

Bartek

[1] quote from pkg-config --help:

  --libs-only-l                                  output -l flags
  --libs-only-other                              output other libs (e.g.
                                                 -pthread)
  --libs-only-L                                  output -L flags
  --cflags                                       output all pre-processor and
                                                 compiler flags
  --cflags-only-I                                output -I flags
  --cflags-only-other                            output cflags not covered by

[2] See below table for incompatible flags that matters for this report:

GCC

CGT

comments

-L<path>

-i=<path>

library search path

-l<name>

-l<fullname>

link against a library/archive/shared object;

GCC guess library name (either lib<name>.so or lib<name>.a)

over 8 years ago

0 George Mock over 8 years ago

TI__Guru**** 244440 points

Bartlomiej Kucharczyk said:
What is your proposed way to solve this incompatibility?

Unfortunately, there isn't one. There is no industry standard regarding a C compiler's command line interface, i.e. the build options, library names, etc. Given that, it is no surprise that the TI compiler and the GCC compiler are very different in these details. They were developed independently, without any regard for compatibility.

All that said, we are aware of this situation. We routinely have internal discussions about matters like this one. Beyond that, there is nothing to announce at this time.

Thanks and regards,

-George