Databases
StackOverflow2013
Postsdbo
PORun time determination of compilation options
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORun time determination of compilation options
    primarykey
    data
    text
    <p>I need to be able to determine at run time what compilation options were use to build the executable. Is there a way to do this?</p> <p><strong>EDIT:</strong> I'm particularly interested in detecting optimization settings. The reason is that I'm writing commercial software that must run as fast as possible. While I am just modifying and testing the system I don't do all the optimizations because it takes too long. But I am worried that I may accidentally go and release an unoptimized version of the program. What I'd like to do is have the program give me a visual warning at start up saying something like "This is the slow version - do not release".</p> <p><strong>EDIT:</strong> Maybe I could write some little utility to run as a pre-build step? Is the command line stored in some file somewhere? If it is then I could extract it, then write it to some include file as a string and hey presto!</p> <p><strong>EDIT:</strong> My choice is not between debug and release. Debug is way too slow - I reserve that strictly for debugging. My day to day choice is between optimized and super-optimized (including the slow-to-compile link time compilation, or even profile guided optimization).</p> <p><strong>EDIT:</strong> I often make changes to the complex compilation process, different libraries, different pre-defined macros, different source files etc. It seems clumsy to have to maintain multiple, almost-identical project files differing only in a couple of optimization flags. I would much prefer to just, as-and-when-required switch a couple of flags in a single project and re-compile. I just want the executable to self test how it was created.</p> <p><strong>EDIT:</strong> IIRC there is some way to ask the visual studio to create a makefile. Can I ask visual studio to create this makefile for me as a pre-build step?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMick
    1. USMick
    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
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORun time determination of compilation options
      1. USMick
      1. VTBountyStart
    2. VO
      singulars
      1. PORun time determination of compilation options
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PORun time determination of compilation options
      1. USforaidt
      1. VTFavorite
    1. COAll of them or specific ones?
      singulars
      1. PORun time determination of compilation options
      1. USMSN
    2. COI am particularly interested in optimization flags.
      singulars
      1. PORun time determination of compilation options
      1. USMick
    3. COThis is standard in the VS build system. You've got a Debug and a Release configuration. You use the former, ship the latter. The DEBUG macro is automatically #defined for the former.
      singulars
      1. PORun time determination of compilation options
      1. USHans Passant
 

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