[Buildroot] svn commit: trunk/buildroot/package/python
ulf.samuelsson at atmel.com
Thu Jan 15 20:11:51 UTC 2009
fre 2009-01-16 klockan 01:01 +1100 skrev Hamish Moffatt:
> On Thu, Jan 15, 2009 at 09:57:41AM +0100, Peter Korsgaard wrote:
> > >>>>> "ulf" == ulf <ulf at uclibc.org> writes:
> > ulf> Author: ulf
> > ulf> Date: 2009-01-15 06:28:05 +0000 (Thu, 15 Jan 2009)
> > ulf> New Revision: 24852
> > ulf> Log:
> > ulf> Always create shared python library, if python is created, needed by multiple packages
> > ulf> +$(STAGING_DIR)/usr/lib/libpython$(PYTHON_VERSION_MAJOR).so: $(TARGET_DIR)/$(PYTHON_TARGET_BINARY)
> > ulf> + cp -dpr $(PYTHON_DIR)/libpython*.so.* $(STAGING_DIR)/usr/lib
> > ulf> + (\
> > ulf> + cd $(STAGING_DIR)/usr/lib ; \
> > ulf> + rm -f libpython$(PYTHON_VERSION_MAJOR).so ; \
> > ulf> + ln -s `basename \`ls libpython*.so.*\`` libpython$(PYTHON_VERSION_MAJOR).so \
> > ulf> + )
> > What are you trying to do here?
Adding libpython, which is required by alsa-lib and all packages
depending on alsa-lib.
There are some more, but guess it is OK to change it
so you can build python without libpython.
The alsa-lib has to depend on libpython and libpython
has to depend on python.
I think there were a few other packages that depended on -lpython2.4 as
well so they will rebreak, but I guess that can be fixed
within a week.
> I'd like to know why libpython is needed, or at least why it's not a
> separate configuration option.
> It's not needed to run python, only to embed it in other applications -
> the main python binary (/usr/bin/python2.x) doesn't even link to it.
> I use Python extensively in my buildroot-based embedded system, and I
> don't need libpython bloating my image.
More information about the buildroot