Databases
StackOverflow2013
Postsdbo
POOut of tree builds with makefiles and static pattern rules
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOut of tree builds with makefiles and static pattern rules
    primarykey
    data
    text
    <p>I'm working on some bare-metal embedded code that runs on ARM, and thus has to deal with the whole ARM vs. THUMB mode distinction. The current build system uses static pattern rules to determine whether to compile files in ARM or THUMB mode. </p> <pre><code>$(ACOBJS) : %.o : %.c @echo $(CC) -c $(CFLAGS) $(AOPT) -I . $(IINCDIR) $&lt; -o $@ $(TCOBJS) : %.o : %.c @echo $(CC) -c $(CFLAGS) $(TOPT) -I . $(IINCDIR) $&lt; -o $@ </code></pre> <p>Where ACOBJS is a list of output objects that should be in ARM mode and the same for TCOBJS and Thumb mode. These lists are created from the list of sources in the usual manner of</p> <pre><code>ACOBJS = $(ACSRC:.c=.o) TCOBJS = $(TCSRC:.c=.o) </code></pre> <p>Currently this results in the object files from the build being strewn about the source tree, which I don't particularly desire. I've been trying to set this up for out of tree builds but haven't been able to get this to work. I don't necessarily need to get full out of tree builds working, but I would like to at least be able to use an output directory under which all the intermediate files end up going. What is the best strategy to achieve this under these constraints?</p> <p>One option I'm considering is using either automake or the whole autotools toolchain to build a makefile. This would seem to support creating the type of makefile I want, but seems like overkill. It also seems like there would be an inherent impedance mismatch between autotools, which is designed for portable builds, and bare-metal embedded systems, where things like host tuple are dictated by the target micro. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmegabytephreak
    1. USmegabytephreak
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOut of tree builds with makefiles and static pattern rules
      1. USmegabytephreak
      1. VTBountyStart
    2. VO
      singulars
      1. POOut of tree builds with makefiles and static pattern rules
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POOut of tree builds with makefiles and static pattern rules
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you want all of the object files, executables and libraries to go into the same output directory?
      singulars
      1. POOut of tree builds with makefiles and static pattern rules
      1. USBeta
    2. COHaving everything end up in the same directory is OK, although not the best case. I currently have this working by replacing the static pattern rules with a target specific addition of the appropriate flags to CFLAGS. https://github.com/MegabytePhreak/power_supply/blob/master/rules.mk shows how I am currently doing things.
      singulars
      1. POOut of tree builds with makefiles and static pattern rules
      1. USmegabytephreak
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload