[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mingw-cross-env-list] How to write .mk for libraries that have no s
From: |
Mark Brand |
Subject: |
Re: [Mingw-cross-env-list] How to write .mk for libraries that have no source releases? |
Date: |
Mon, 22 Nov 2010 20:26:20 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.1.6 Thunderbird/3.1.6 |
On 11/22/2010 03:19 PM, DiAppoggio wrote:
Hi,
I'd like to write a .mk for a library which is only git available (
http://www.videolan.org/developers/libbluray.html ).
How can I write $(PKG)_URL variable and $(PKG)_UPDATE section?
Thanks!
That's a good question that hasn't really come up yet. Since there
really is no package tarball, there should some kind of null $(PKG)_URL,
maybe pointing to /dev/null. The commits from the git repo could be
packaged using 'git format-patch -p'. The patch would be applied during
the build to an empty directory. The patch in src/qt-1-win32.patch is an
example of how this is done, the difference being that this patch is
applied to the package tarball contents instead of to an empty directory.
Not sure what to do about $(PKG)_UPDATE for this case.
That's just my two cents' worth. Curious to see what answers will be.
Mark