I am trying to build Microsoft visual c++ programs at the command line using
GNU MAKE. The msdn library says that If you have a project that you build
from the command line with a make file, then the Visual Studio development
environment will not recognize your project. This is because visual studi
On Thu, 2007-05-17 at 11:17 +0530, chandan wrote:
> I am trying to build Microsoft visual c++ programs at the command line
> using GNU MAKE. The msdn library says that If you have a project that
> you build from the command line with a make file, then the Visual
> Studio development environment wil
Hi,
I'm using version GNU make v3.79.1 on HP-UX 10.20. I'm having a few
problems with a makefile, the root of the problem seems to be connected
with the $(shell) function. I wonder if you could offer any suggestions?
Basically, I want to set an environment variable according to the
contents of a
%% [EMAIL PROTECTED] writes:
tm> Now it gets a little more complicated because the contents of
tm> INFO_FILE get modified during the build, and I only want to
tm> evaluate FOO after INFO_FILE has been modified However what I'm
tm> finding is that if I modify the contents of INFO_FILE and
[EMAIL PROTECTED] wrote:
>
> All the variables and functions in a rule script are evaluated before
> the first line is run. For example, in:
>
> foo:
> echo $(FOO)
> echo $(BAR)
>
> Make goes:
>
> evaluate FOO, evaluate BAR, run echo $(FOO), run echo $(BAR)
>
> and NOT:
%% [EMAIL PROTECTED] writes:
tm> Every time I build an executable I append some information about the
tm> build to a log file. This is done with a perl script called in one of
tm> the makefile rules. The script tags this information with a unique
tm> serial number, and sends this number t