[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 139457] It is impossible to manually add files to a project of
From:       Claus Wilke <wilke () spamcop ! net>
Date:       2007-01-01 17:06:55
Message-ID: 20070101170655.32411.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=139457         
wilke spamcop net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |



------- Additional Comments From wilke spamcop net  2007-01-01 18:06 -------
I don't think your answer addresses my point. The automake manager assumes that every \
source file is listed for some standard automake target. However, there may be cases \
where no suitable automake target exists. For example, the Makefile.am for my python \
bindings looks something like this: ## Makefile.am
all: $(top_builddir)/src/foo/libfoo.a
        python setup.py build

install: $(top_builddir)/src/foo/libfoo.a
        python setup.py install

clean:
        rm -rf build
        rm -f *.pyc

maintainer-clean: clean
        rm Makefile Makefile.in

Clearly, there is no suitable automake target to which I can add the C or C++ sources \
that are part of the python bindings, and thus the current automake manager doesn't \
allow me to add these sources.


[prev in list] [next in list] [prev in thread] [next in thread]