[sane-devel] Compiling: make doesn't do anything?

2005-10-26 Thread Patrick Lessard 
It works with the make depend.

Thanks Stephane!


 -Message d'origine-
 De : sane-devel-boun...@lists.alioth.debian.org
 [mailto:sane-devel-boun...@lists.alioth.debian.org]De la part de
 St?phane VOLTZ
 Envoy? : 24 octobre, 2005 15:56
 ? : sane-devel@lists.alioth.debian.org
 Objet : Re: [sane-devel] Compiling: make doesn't do anything?
 
 
   Hello,
 
   shouldn't the 'depend' target take care of dependencies 
 ? After a 'make 
 depend', everything should work fine.
 
   You can avoid installing each time by using the 
 LD_PRELOAD environment 
 variable and running xsane from the backend subdir:
 
 export LD_PRELOAD=.libs/libsane-mybackend.so.1.0.16
 
 Regards,
   Stef
 
 -- 
 sane-devel mailing list: sane-devel@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
  to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] Compiling: make doesn't do anything?

2005-10-26 Thread Henning Meier-Geinitz 
Hi,

On Mon, Oct 24, 2005 at 09:55:36PM +0200, St?phane VOLTZ wrote:
   shouldn't the 'depend' target take care of dependencies ? After a 'make 
 depend', everything should work fine.

Looks like that really works. i have never tried it before.

Should we run make depend by default (if makedepend is available)?

Bye,
  Henning

[sane-devel] Compiling: make doesn't do anything?

2005-10-24 Thread Patrick Lessard 
Hello,

1- Everytime I do a modification on the .c file, when I do make, it says,
nothing to do for 'all'? I have to do a make -B, but this recompile
everything and it's taking too long.

2- Also, to test my modifications, I do a make install. After that I start
xsane, but how can I make sure that xsane is really using the new library?
Is there some cache somewhere that I should clear?

3- Where do I enable/disable to logging when setting the ENV Var of a
particular backend?

I'm using Fedora 4 and I disabled prelinking.

Any idea?

Thank you.

Patrick.

[sane-devel] Compiling: make doesn't do anything?

2005-10-24 Thread Henning Meier-Geinitz 
Hi,

On Mon, Oct 24, 2005 at 01:28:34PM -0400, Patrick Lessard wrote:
 1- Everytime I do a modification on the .c file, when I do make, it says,
 nothing to do for 'all'? I have to do a make -B, but this recompile
 everything and it's taking too long.

This happens if you change a .c file that is not a main file, i.e.
that is included by some other C-file. There has been some discussion
about this behaviout and possible solutions, but nobody has
implemented anything yet. If you are interested, search the archive.
The work around is to touch (or edit) the main file. E.g. if yo fiddle
with gt69xx_devices.c, touch gt68xx.c and run make.

 2- Also, to test my modifications, I do a make install. After that I start
 xsane, but how can I make sure that xsane is really using the new library?
 Is there some cache somewhere that I should clear?

You could put a debug print in sane_init, e.g.

DBG(0, This is actually Patrick Lessard's code\n);

and check if it's printed in the teminal you run xsane from.

 3- Where do I enable/disable to logging when setting the ENV Var of a
 particular backend?

E.g. for the gt68xx backend, enter in a terminal window:

export SANE_DEBUG_GT68xx=255 (enables all debugging)
xsane

Bye,
  henning

[sane-devel] Compiling: make doesn't do anything?

2005-10-24 Thread Patrick Lessard 
Hi,

 -Message d'origine-
 De : sane-devel-boun...@lists.alioth.debian.org
 [mailto:sane-devel-boun...@lists.alioth.debian.org]De la part 
 de Henning
 Meier-Geinitz
 Envoy? : 24 octobre, 2005 13:47
 ? : sane-devel@lists.alioth.debian.org
 Objet : Re: [sane-devel] Compiling: make doesn't do anything?
 
 
 Hi,
 
 On Mon, Oct 24, 2005 at 01:28:34PM -0400, Patrick Lessard wrote:
  1- Everytime I do a modification on the .c file, when I do 
 make, it says,
  nothing to do for 'all'? I have to do a make -B, but this recompile
  everything and it's taking too long.
 
 This happens if you change a .c file that is not a main file, i.e.
 that is included by some other C-file. There has been some discussion
 about this behaviout and possible solutions, but nobody has
 implemented anything yet. If you are interested, search the archive.
 The work around is to touch (or edit) the main file. E.g. if yo fiddle
 with gt69xx_devices.c, touch gt68xx.c and run make.

ok got it.

 
  2- Also, to test my modifications, I do a make install. 
 After that I start
  xsane, but how can I make sure that xsane is really using 
 the new library?
  Is there some cache somewhere that I should clear?
 
 You could put a debug print in sane_init, e.g.
 
 DBG(0, This is actually Patrick Lessard's code\n);
 
 and check if it's printed in the teminal you run xsane from.


Great idea, I'll do that.

 
  3- Where do I enable/disable to logging when setting the 
 ENV Var of a
  particular backend?
 
 E.g. for the gt68xx backend, enter in a terminal window:
 
 export SANE_DEBUG_GT68xx=255 (enables all debugging)
 xsane
 

ok, but it says in the man page If  the  library  was  compiled with debug
support enabled.

Where can I check this?

Thanks.

Patrick.


 Bye,
   henning
 
 -- 
 sane-devel mailing list: sane-devel@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
  to sane-devel-requ...@lists.alioth.debian.org

[sane-devel] Compiling: make doesn't do anything?

2005-10-24 Thread Stéphane VOLTZ 
Hello,

shouldn't the 'depend' target take care of dependencies ? After a 'make 
depend', everything should work fine.

You can avoid installing each time by using the LD_PRELOAD environment 
variable and running xsane from the backend subdir:

export LD_PRELOAD=.libs/libsane-mybackend.so.1.0.16

Regards,
Stef