[Q-e-developers] makedeps.sh

[Layla Martin-Samos]

Dear Riccardo, makedeps.sh creates files make.depend in espresso dirs, that
are in any case included in the distribution (users never need to run
makedeps.sh). makedeps.sh is used if you change the dependencies of
routines, or you add new routines with dependencies. It is only a tool used
for development. When you make disclean in probably does not work properly
because it needs the specification of $TOPDIR (see make.sys and configure.ac).


What do you mean about fooled by "#include "something.f90"" ?

bests

Layla

2011/4/19 Riccardo Di Meo <dimeo at democritos.it>

> Dear all,
>
> I'm working on a package that requires espresso in order to work
> (namely, the MS2 subsystem) and since some of the files that I need to
> include in espresso while compiling have many dependencies, I was
> wondering about the purpose of some files in the install directory.
>
> In particular, the file makedeps.sh came to my attention and I was
> asking myself if it is supposed to be used by some configure related
> script dynamically (e.g. it takes a part in the installation process
> while the user configures and compiles the espresso package) or if the
> script is there just for the developers convenience (to simplify the
> process of finding out and configure the distribution). Could you please
> tell me which scenario is correct (if any)?
>
> I have also noticed that such script seems to work fine if the espresso
> source tree is at least partially compiled (at least up to the iotk) but
> it seems not to work if I start from a fresh directory/distclean
> configuration. Am I missing a preliminary step, or being it probably a
> developer utility is it supposed to work in that way?
>
> Last thing: using the aforementioned trick (configure/make and then
> makedeps.sh) the scipt seems to work fine, however, at least in my case,
> looks like it's fooled by an #include "something.f90" which I have in my
> code (I know it isn't good practice, however it avoids a circular
> dependency): is there a way to work around this?
>
> Thank you in advance
> Cheers,
> Riccardo Di Meo
>
> --------------
> SISSA
> _______________________________________________
> Q-e-developers mailing list
> Q-e-developers at qe-forge.org
> http://qe-forge.org/mailman/listinfo/q-e-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quantum-espresso.org/pipermail/developers/attachments/20110419/72ddbca2/attachment.html>