Databases
StackOverflow2013
Postsdbo
POSCons: Separate debug/release build dirs with a hierarchical build
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSCons: Separate debug/release build dirs with a hierarchical build
    primarykey
    data
    text
    <p>I just started learning to use SCons, anticipating that it solves some of my issues with make. I'm creating a source hierarchy to understand the basics of SCons.</p> <p>Let's start with this folder structure:</p> <ul> <li>test/foo: contains main.cpp, main.h</li> <li>test/bar: contains its own main.cpp, main.h</li> <li>test/common: contains utils.cpp and utils.h used by both foo and bar</li> <li>test/external/moo: the source to some external library, containing 'configure' which produces 'Makefile' (not using SCons), so SCons needs to invoke 'make' after 'configure'; I suspect this part might be tricky when build dirs are used</li> <li>test/build/debug: build dir for debug</li> <li>test/build/release: build dir for release</li> </ul> <p>Here's what I'd like to do:</p> <ul> <li><p>Have two types of builds: debug/release where the only difference is that debug specifies -DDEBUG to g++</p></li> <li><p>Use build dirs so that no .o files are created in my source tree. Let's call these build dirs "build/debug" and "build/release"</p></li> <li><p>Be able to invoke ./configure and make on another project that does not use SCons, followed by linking libmoo.a it produces with my project</p></li> <li><p>Have the builds be perfectly parallel (scons -j9 for an 8-core?)</p></li> <li><p>Have some debug/release-independent way of specifying libraries to link. Something like:</p> <pre><code>env.Program(target='foo', source=['foo/main.cpp', '#build/(DEBUG_OR_RELEASE)/lib/libsomething.a']) </code></pre></li> </ul> <p>What would the very basic SConstruct/SConscript files to do the above look like? Even just pointers in the right directions would be great too!</p> <p>Thanks in advance :-)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USPavel
    plurals
    1. This table or related slice is empty.
    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. POSCons: Separate debug/release build dirs with a hierarchical build
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSCons: Separate debug/release build dirs with a hierarchical build
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOne way to do it is to pass an option to scons. scons does support command line options, though it looks like you can't use a short form. Then have two versions of everything depending whether that flag is present.
      singulars
      1. POSCons: Separate debug/release build dirs with a hierarchical build
      1. USFaheem Mitha
 

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