Hello Ralf,
On Tue, Dec 22, 2009 at 07:21:44AM +0100, Ralf Wildenhues wrote:
> > Now, the files are copied into a single destination directory. I'd like
> > to distribute the files preserving their paths...
>
> Use nobase_python_PYTHON.
This works great, thanks!
Now, how can I exclude the sourc
Hi Baurzhan,
* Baurzhan Ismagulov wrote on Tue, Dec 22, 2009 at 12:51:33AM CET:
> I've created a Makefile.am to compile and install Python files.
>
> Now, the files are copied into a single destination directory. I'd like
> to distribute the files preserving their paths, i.e., the structure
>
>
Hello,
I've created a Makefile.am to compile and install Python files.
Now, the files are copied into a single destination directory. I'd like
to distribute the files preserving their paths, i.e., the structure
pkg/
a.py
b.py
c/
d.py
e.py
should be reproduced under /usr/lib/python
Ralf Wildenhues wrote on 21/12/2009 22:14:51:
>
> * Joakim Tjernlund wrote on Sun, Dec 20, 2009 at 03:58:47PM CET:
> > Yes, thanks for the script layout. What would be even
> > cooler is if one could add a custom macro in acinclude.m4
> > that would override the libtool.m4 macro creating the -fPIC
* Joakim Tjernlund wrote on Sun, Dec 20, 2009 at 03:58:47PM CET:
> Yes, thanks for the script layout. What would be even
> cooler is if one could add a custom macro in acinclude.m4
> that would override the libtool.m4 macro creating the -fPIC option
> and replace it with -fpic instead.
No, it woul
