Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If I were you I'd think twice before migrating the build within the IDE. I understand that seems more confortable to you, but the builtin build facilities are really limited.</p> <p>Visual Studio's builtin build system <strong>does not scale</strong> ! When your project reaches a certain size, it becomes more of a hindrance than anything else. Microsoft recognizes this fact and currently pushes for their alternative called <em>MSBuild</em>.</p> <p>Try modifying a compile option when your solution contains over 80 different subprojects... It's a mouse clic fest, tedious and error prone...</p> <p>At this point you'll have the following options :</p> <ol> <li>Editing the project files manually (still an awful lot of files).</li> <li>Generating the Visual Studio solution from a description.</li> <li>Integrate an alternative build system within the IDE (if that exists).</li> <li>Using a more adequate external build system and call it from the IDE (you also get the opportunity to become cross platform).</li> </ol> <p>These are make variants (build is driven by Makefiles or similar):</p> <ul> <li>nmake: probably the least powerful, windows only</li> <li>OMake: cross platform (nice)</li> <li>Scons: cross platform (never used it)</li> <li>CMake: cross platform (never used it)</li> <li>Rake: cross platform (sucks)</li> <li>gmake: cross platform but expect issues with paths on windows (comes from the 'nix world)</li> </ul> <p>These are ant variants (build is driven by xml descriptions instead of makefiles):</p> <ul> <li>nant</li> <li>MSBuild (from Microsoft)</li> </ul> <p>Anyway, remember that compiling outside the IDE does <strong>not</strong> prevent you from using it for editing, debugging (and the debugger is nice) and so on !</p> <p>Regarding your issue, you forgot to add the libraries listed in the following excerpt:</p> <pre><code>TAMLIB = $(LIBDIR)\tam_$(NAMETAG).lib TAMCLIB = $(LIBDIR)\tamc_$(NAMETAG).lib MMSLIB = $(LIBDIR)\mmsc_$(NAMETAG).lib </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POImport Makefile settings to VS2005 IDE
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USbltxd
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POImport Makefile settings to VS2005 IDE
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI was told to migrate to VS IDE because i have to integrate the codes above with a DDK configured for VS 2005 C++. Option 4 is very interesting. I need to google up on this. Does that mean that i can call OMAKE(for example) from VS IDE to read the makefile and build the exe? or it is just using a different build system? it doesnt use makefiles and i have input the compiler and linker options to the IDE?
      singulars
      1. PO
      1. USjustin
    2. COCould you elborate more about about your answer "compiling outside the IDE does not prevent from using it for debugging". I can use breakpoints and setting up watch?
      singulars
      1. PO
      1. USjustin
    3. CO@justin, comment 2: The IDE can be used to debug any program. You start with a solution for a C++ program or library, just fill in the debug settings (path, command-line options, source directories) and you're done.
      singulars
      1. PO
      1. USbltxd
 

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