If `file1` does not exist then `$(wildcard file1)` will evaluate to an empty string.

    ifeq ($(wildcard file1),) 
        CLEAN_SRC =
    else 
        CLEAN_SRC = *.h file3
    endif 

Why is Java&#39;s `Class&lt;T&gt;` generic?

Why is Java&#39;s Class&lt;T&gt; generic?

I want to create an installer EXE with some specific properties:

1. it should be a single exe file
2. it should be robust (i.e. the technique should be known to work well on any Windows system)
3. it should create only a single file (a .scn screensaver file) in %systemroot%
4. it should add the option to uninstall that particular file in &quot;Control Panel -&gt; Add or Remove Programs&quot; but without creating any new entry `C:\Program Files` or copying an uninstaller.exe somewhere.

I&#39;ve seen installers that work like that - so how to do this?


How to create a robust, minimal installer for Windows?

For example:
I want:

if file1 exists:

    CLEAN_SRC = *.h file3

else

    CLEAN_SRC = 

How to conditional set up a Makefile variable by testing if a file exists

For example:
I want:
if file1 exists:
<pre><code class="hljs language-ini">CLEAN_SRC = *.h file3
</code></pre>
else
<pre><code class="hljs language-makefile">CLEAN_SRC = 
</code></pre>

I have the following makefile for my project, and I&#39;d like to configure it for release and debug builds. In my code, I have lots of `#ifdef DEBUG` macros in place, so it&#39;s simply a matter of setting this macro and adding the `-g3 -gdwarf2` flags to the compilers. How can I do this?

    $(CC) = g++ -g3 -gdwarf2
    $(cc) = gcc -g3 -gdwarf2
    
    all: executable
    
    executable: CommandParser.tab.o CommandParser.yy.o Command.o
    	g++ -g -o output CommandParser.yy.o CommandParser.tab.o Command.o -lfl
    
    CommandParser.yy.o: CommandParser.l 
    	flex -o CommandParser.yy.c CommandParser.l
    	gcc -g -c CommandParser.yy.c
    
    CommandParser.tab.o: CommandParser.y
    	bison -d CommandParser.y
    	g++ -g -c CommandParser.tab.c
    
    Command.o: Command.cpp
    	g++ -g -c Command.cpp
    
    clean:
    	rm -f CommandParser.tab.* CommandParser.yy.* output *.o

Just to clarify, when I say release/debug builds, I want to be able to just type `make` and get a release build or `make debug` and get a debug build, without manually commenting out things in the makefile.


How can I configure my makefile for debug and release builds?

I have a project where the directory structure is like this:

                             $projectroot
                                  |
                  +---------------+----------------+
                  |               |                |
                part1/          part2/           part3/
                  |               |                |
           +------+-----+     +---+----+       +---+-----+
           |      |     |     |        |       |         |
         data/   src/  inc/  src/     inc/   src/       inc/


How should I write a makefile that would be in part/src (or wherever really)  that could comple/link on the c/c++ source files in part?/src ?

Can I do something like
-I$projectroot/part1/src -I$projectroot/part1/inc -I$projectroot/part2/src ...

If that would work, is there an easier way to do it.  I&#39;ve seen projects where there is a makefile in each of the corresponding part? folders.  [in this post I used the question mark like in bash syntax]

Makefiles with source files in different directories

I am trying to understand the difference between &#39;gmake&#39; and &#39;make&#39;?  

On my linux box they are identical:

    % gmake --version
    GNU Make 3.81
    Copyright (C) 2006  Free Software Foundation, Inc.
    This is free software; see the source for copying conditions.
    There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
    PARTICULAR PURPOSE.

    % make --version
    GNU Make 3.81
    Copyright (C) 2006  Free Software Foundation, Inc.
    This is free software; see the source for copying conditions.
    There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
    PARTICULAR PURPOSE.

I am guessing this isn&#39;t the same on all platforms?
Is there a good reason to use one over the other?  
Is there some historical significance to why there are the two names?




What is the difference between gmake and make?

I must be missing something really obvious, but for some reason, the command-line version of the Microsoft C++ compiler (cl.exe) does not seem to support reporting just its version when run.  We need this to write makefiles that check the compiler version a user of our tool has installed (they get makefiles with code they are to compile themselves locally, so we have no control over their compiler version). 

In gcc, you just give the option -v or --version to get a nice version string printed. 

In cl.exe, you get an error for -v. 

I have read the MSDN docs and compiler online help, and I cannot find the switch to just print the compiler version.  Annoyingly, you always get the version when the compiler starts... but you seem not to be able to start the compiler just to get the version out of it.

https://stackoverflow.com/questions/801279/finding-compiler-vendor-version-using-qmake seemed similar, but only deals with the simple case of gcc. 

I am trying this with VC++ Express 2005, if that matters. I hoped it would not, as detecting the compiler version is best done in a compiler-version-independent way :) 

Update, after replies:

 - Running cl.exe without any arguments
   prints its version and some help
   text.  
 - This looks like the most
   portable way to get at the version,
   across vc versions. 
 - You then have to
   parse a multi-line output, but that
   is not too difficult. 
 - We did this in
   the end, and it works.



Finding version of Microsoft C++ compiler from command-line (for makefiles)

I&#39;m trying to figure out the best build system for latex.

Currently, I use [latex-makefile][1], editing in vim, and viewing changes in Okular or gv. The major problem is that it sometimes gets hides errors on me, and I have to run latex manually. The major advantages are that it does all the iteration I need, and offers both pdf and ps simply.

If you have experience with

   * latex-mk
   * vim-latex
   * kile
   * lyx
   * miktex
   * latex-makefile
   * the ultimate latex makefile
   * rubber
   * any others I havent come across

Would you recommend them, and why/why not?


  [1]: http://code.google.com/p/latex-makefile


Content Type	Original Author	Original Content on Stackoverflow
Question	Sam Liao	View Question on Stackoverflow
Solution 1 - Makefile	John Kugelman	View Answer on Stackoverflow

How to conditional set up a Makefile variable by testing if a file exists

Makefile Problem Overview

Makefile Solutions

Solution 1 - Makefile

How to create a robust, minimal installer for Windows?

Why is Java's Class<T> generic?

Attributions