Subject: Re: [Boost-build] Embedded ARM GNU 8.2.1 Archive Fail on Lib Target
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2019-02-12 02:10:40
On 2/11/19 6:27 PM, codex653 via Boost-build wrote:
> Hey all. I've been learning the Boost.Build system for embedded projects at
> work and am attempting to use it for some of my own projects at home with
> some of the STM32 series chips. I've run into quite a strange issue that has
> puzzled some more experienced boost users at work, so I wanted to post
> something here and try my luck.
> 1. In my Jamroot.jam, I cannot have "use-project /STM32F7 :
> <relative_path_to_prj> ;" defined
> or else I will get the error message. If I take this out, my problem
> goes away.
> 2. The path length to the .o files matters quite a bit. If I place my
> Jamroot.jam one directory above the Jamfile which contains the HAL_DRIVER
> lib that is being built, I have no issues. HOWEVER, if I give that directory
> an absurdly long name, say 25 characters or so, it will break again.
> 3. The number of .o files being archived matters. Specifically in my
> case, I could only archive 51 at a time. Any more than that (it didn't
> matter which file), and it would break again.
It sounds like the command line is too long and is being
truncated. Boost.Build tries to protect against this,
but it seems to be not working for unknown reasons.
If run the link command directly, does it work?
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk