vpath Question

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

vpath Question

Bhaskar G

Hi All,

I had a question on vpath directive.

In one of my makefile I have the following entry
vpath %.lib $(_SDE_DIR_LIB)  

_SDE_DIR_LIB expands to d:/results/x86_nt/comps/generated/lib/x86_nt_el_i486

I am using gmake provided by cygwin and gmake built on my machine using the source.

I get the following error when using gmake provided by cygwin:

            Considering target file `libtmComp2_flo_g.lib'.
             File `libtmComp2_flo_g.lib' does not exist.
             Looking for an implicit rule for `libtmComp2_flo_g.lib'.
             No implicit rule found for `libtmComp2_flo_g.lib'.
             Finished prerequisites of target file `libtmComp2_flo_g.lib'.
            Must remake target `libtmComp2_flo_g.lib'.
gmake: *** No rule to make target `libtmComp2_flo_g.lib', needed by `d:/results/x86_nt/comps/generated/lib/x86_nt_el_i486/_flo_sp_g/tmComp10.dll'.  Stop.

Where as this problem doesnot seem to appear when using the gmake built locally.

            Considering target file `libtmComp2_flo_g.lib'.
             Looking for an implicit rule for `libtmComp2_flo_g.lib'.
             No implicit rule found for `libtmComp2_flo_g.lib'.
             Finished prerequisites of target file `libtmComp2_flo_g.lib'.
            No need to remake target `libtmComp2_flo_g.lib'; using VPATH name `d:/results/x86_nt/comps/generated/lib/x86_nt_el_i486/libtmComp2_flo_g.lib'.

My question is Can the vpath directive be removed optionally when building gmake?

Thanks & Regards,
Bhaskar G
=================================================
Philips Semiconductors / CTO / Design Technology Group

E-mail:        [hidden email]
Phone:       +91 80 2557 9000, Ext 3016
Fax:            +91 80 2556 0581
GSM:         +91 944 876 1340

Office:        Philips Innovation Campus, 3rd floor
Address:   No 1, Murphy Road, Ulsoor, Bangalore - 560 008
Country:    INDIA
=================================================

_______________________________________________
Help-make mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-make
Reply | Threaded
Open this post in threaded view
|

Re: vpath Question

Paul Smith-20
%% Bhaskar G <[hidden email]> writes:

  bg> In one of my makefile I have the following entry
  bg> vpath %.lib $(_SDE_DIR_LIB)

  bg> _SDE_DIR_LIB expands to
  bg> d:/results/x86_nt/comps/generated/lib/x86_nt_el_i486

  bg> I am using gmake provided by cygwin and gmake built on my machine
  bg> using the source.

  bg> I get the following error when using gmake provided by cygwin:

  bg>             Considering target file `libtmComp2_flo_g.lib'.
  bg>              File `libtmComp2_flo_g.lib' does not exist.
  bg>              Looking for an implicit rule for `libtmComp2_flo_g.lib'.
  bg>              No implicit rule found for `libtmComp2_flo_g.lib'.
  bg>              Finished prerequisites of target file `libtmComp2_flo_g.lib'.
  bg>             Must remake target `libtmComp2_flo_g.lib'.
  bg> gmake: *** No rule to make target `libtmComp2_flo_g.lib', needed by
  bg> `d:/results/x86_nt/comps/generated/lib/x86_nt_el_i486/_flo_sp_g/tmComp10.dll'.
  bg>  Stop.

  bg> Where as this problem doesnot seem to appear when using the gmake built
  bg> locally.

  bg>             Considering target file `libtmComp2_flo_g.lib'.
  bg>              Looking for an implicit rule for `libtmComp2_flo_g.lib'.
  bg>              No implicit rule found for `libtmComp2_flo_g.lib'.
  bg>              Finished prerequisites of target file `libtmComp2_flo_g.lib'.
  bg>             No need to remake target `libtmComp2_flo_g.lib'; using VPATH
  bg> name
  bg> `d:/results/x86_nt/comps/generated/lib/x86_nt_el_i486/libtmComp2_flo_g.lib'.

  bg> My question is Can the vpath directive be removed optionally when
  bg> building gmake?

No, that's not possible.

Please note that the Cygwin version of GNU make has had some
cygwin-specific patches applied to it: it's not a vanilla GNU make.
Thus, it might behave differently than vanilla GNU make.  The folks on
this list generally don't have any experience with Cygwin GNU make.  If
you think the problem is with Cygwin's version you need to contact
them.  If you think the problem is with vanilla GNU make, please provide
a description of the problem you see and why you think it's a problem
that _doesn't_ rely on knowledge of how Cygwin GNU make works.


Cheers!

--
-------------------------------------------------------------------------------
 Paul D. Smith <[hidden email]>          Find some GNU make tips at:
 http://www.gnu.org                      http://make.paulandlesley.org
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist


_______________________________________________
Help-make mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-make