You have to do something to catch the /showIncludes text during the compiles,
process it into a %.mk file, and optionally include it.
At least that is what we had to do years ago before they added these types of
options.
There is also the /Gm option, but I'm not that familiar with the idb files
I tried it on solaris and found that it was broken there too. The output
from the -xMMD compiler option that we use is not compatible with our
makefiles. The object file is printed without directories, just the file
name. Adding this to the bug.
/Erik
On 2013-04-08 19:10, Phil Race wrote:
FW
You can't feed make with the /showInclude output. There's a dedicated
tool in Cygwin (and on *NIX in general) - makedepend. It produces output
that make can parse and understand directly.
--
best regards,
Anthony
On 4/8/2013 20:00, Kelly O'Hair wrote:
I think it's /showIncludes ???
http://msd
FWIW, I was on Solaris 10 SPARC.
I sent you a separate email off-list since what I saw is that the case you
described does actually work but one that is different - in closed
sources - didn't work.
-phil.
On 4/8/2013 9:00 AM, Kelly O'Hair wrote:
I think it's /showIncludes ???
http://msdn.mic
I think it's /showIncludes ???
http://msdn.microsoft.com/en-us/library/hdkef6tk%28v=vs.100%29.aspx
-kto
On 4/8/13 1:16 AM, "Erik Joelsson" wrote:
>I just realized you are probably running on windows and unfortunately
>this currently doesn't work there. We use the -M flag for gcc which
>outputs
I just realized you are probably running on windows and unfortunately
this currently doesn't work there. We use the -M flag for gcc which
outputs make dependency files. The visual studio compiler doesn't have
this feature. There are ways this can be worked around. I've created
8011687 to track
On 2013-03-29 00:00, Phil Race wrote:
> If you touch a header fie, the build is supposed to notice and "do
the right thing".
It did not do so. If I touched a C file, no problem, but not so for
the header file.
This was observed on Solaris 10 SPARC.
I just tried:
touch ../../jdk/src/share/
On 29/03/2013 7:29 AM, Phil Race wrote:
1. Why do we have both --with-cups and --with-cups-include ?
All we use is the header files so the latter is what matters and
I'm not sure which one the build system prefers if both are set.
2. In the old build I could do
cd make/sun/font
make clea
On Mar 28 2013, at 14:29 , Phil Race wrote:
> 1. Why do we have both --with-cups and --with-cups-include ?
> All we use is the header files so the latter is what matters and
> I'm not sure which one the build system prefers if both are set.
You will often see this style in configure scripts. It
> If you touch a header fie, the build is supposed to notice and "do
the right thing".
It did not do so. If I touched a C file, no problem, but not so for the
header file.
This was observed on Solaris 10 SPARC.
-phil.
On 3/28/2013 2:45 PM, Jonathan Gibbons wrote:
On 03/28/2013 02:29 PM, Phi
On 03/28/2013 02:29 PM, Phil Race wrote:
1. Why do we have both --with-cups and --with-cups-include ?
All we use is the header files so the latter is what matters and
I'm not sure which one the build system prefers if both are set.
2. In the old build I could do
cd make/sun/font
make clean
11 matches
Mail list logo
