using GOA to port libraries

[Pirmin Duss]

Hi Norman

On 11/11/22 09:05, Norman Feske wrote:
> Hi Pirmin,
> 
> as a word of caution, we haven't used Goa for the porting of libraries 
> yet. In particular, the linking arguments for building shared objects 
> are currently not handled by Goa. Goa is also not equipped with a way to 
> publish a library's ABI (symbol file + headers). We eventually want to 
> go in this direction, but you are the first. ;-)

 From what I had seen before, I already had guessed, that that might be 
the case. Thanks for the information, that is good to know.

>> If I issue `goa build` successfully runs `cmake` but building fails 
>> afterward. There are a lot of `[-Werror=effc++]`.
>>
>> I tired different ways to set `CC_CXX_WARN_STRICT=` in the files 
>> `cmake_args` and `make_args`. Unfortunately none of them helped.
> 
> The strict default can be overridden in the two following ways.
> 
> 1. Telling goa to be less strict at the command line:
> 
>     $ goa build --no-warn-strict
> 
> 2. Placing a .goarc file in your project directory with the
>     following line:
> 
>     set warn_strict 0

This works like a charm.

> BTW, while investigating your question, I noticed a slight inconsistency 
> in the documentation of Goa's configuration ('goa help config') that I 
> fixed just now. So thanks for bringing up the topic.

happy to help :-)

Regards
Pirmin

-- 
Pirmin Duss
Founder and Senior Software Engineer
gapfruit AG
Baarerstrasse 135
CH-6300 Zug
pirmin.duss at gapfruit.com