| Hi Felipe,
Thanks for the info! Somehow the patch I created from git didn't
apply cleanly. I did the quilt commands and it seemed to be alright,
but this is all new to me. When I ran "dpkg-buildpackage -us -uc -j2"
it failed though in trying to apply that patch I created.
Perhaps at this point, I should leave this in the hands of
professionals. :P (Though, I just realized, I could make a patch from
the diff between what is in that repo and what is in head of csound5;
unfortunately, I have to stop for today...).
Thanks!
steven
On Mon, Sep 24, 2012 at 5:36 PM, Felipe Sateler wrote:
> Building should be easy, although a bit cumbersome. The workflow in
> this case should be:
>
> 1. Grab the package source (apt-get source csound), and cd into the sources.
> 2. Copy the patch into the debian/patches directory (named something
> like 000x-swig-java-package-flag.patch[1]), and add the filename to
> the file debian/patches/series, keeping the numeric sort.
> 3. Refresh all patches. Use "quilt push && quilt refresh" repeatedly
> until all patches are refreshed[2].
> 3. Add a new changelog entry with "dch -i" (from the package devscripts).
> 4. Build the package with "dpkg-buildpackage -us -uc -j2)" (-j2 is to
> use 2 threads for building,similar to make or scons). This will abort
> if there are missing build-dependencies, telling you which packages
> you need to install.
> 5. The packages are in the parent directory of the package sources
> (ie, the path where you executed apt-get source).
>
> I hope this makes it clear
>
> [1] We prefix patches with 0xxx if they come from the main csound
> repository, which is the case here, 1xxx if they should be applied to
> the main repo but are not yet, and 2xxx for debian-specific patches.
> [2] The debian build tools abort if any patches do not apply cleanly.
> Since the patch was inserted in the middle of the series, some later
> patches could apply fuzzily or even not at all.
>
> On Mon, Sep 24, 2012 at 12:20 PM, Steven Yi wrote:
>> It did for me here, at least with my beta version of blue. Someone on
>> the blue mailing list reported an issue with their build but they were
>> using scons (worked with the blue beta, but not 2.2.0). I feel alright
>> that this is working now. (I had compared the symbol names using nm
>> and they looked the same now as the ones generated from scons).
>>
>> Would it be best to build a test deb pkg and have me test it here?
>> Also, are there instructions for building a deb?
>>
>> Thanks!
>> steven
>>
>> On Mon, Sep 24, 2012 at 5:13 PM, Felipe Sateler wrote:
>>> Great! So, after this change does blue work with libcsnd-java? As I've
>>> never used the java interface I always wondered if it really worked...
>>>
>>> On Mon, Sep 24, 2012 at 12:10 PM, Steven Yi wrote:
>>>> Hi Felipe,
>>>>
>>>> No worries about the delay, very much understand! (And thanks, as
>>>> usual, for all of your work on Debian!) The commit that fixes things
>>>> is:
>>>>
>>>> http://csound.git.sourceforge.net/git/gitweb.cgi?p=csound/csound5.git;a=commit;h=d7c372b0237ba9aecdd965f1f10eb6e527b7ec52
>>>>
>>>> which fixes the use of "-package csnd" when compiling the java part of
>>>> the library.
>>>>
>>>> Thanks again!
>>>> steven
>>>>
>>>> On Mon, Sep 24, 2012 at 5:04 PM, Felipe Sateler wrote:
>>>>> Hi, sorry for the delay, I was away.
>>>>>
>>>>> On Fri, Sep 21, 2012 at 4:35 PM, Steven Yi wrote:
>>>>>> Update: I think I have fixed this. Turns out Cmake was not calling
>>>>>> swig correctly to use "-package csnd" and therefore the generated lib
>>>>>> and jar were incorrect. I have pushed a fix to GIT. I'm going to
>>>>>> guess that the Debian/Ubuntu build used CMake due to the same lack of
>>>>>> csnd package.
>>>>>
>>>>> Yes, I'm using cmake. Great that you have a fix!
>>>>>
>>>>>>
>>>>>> Felipe: How do things work for Debian to get a bug fix like this in
>>>>>> for a release?
>>>>>
>>>>> For debian, the usual procedure is to file a bug with severity serious
>>>>> against the libcsnd-java package. The maintainer then should
>>>>> negotiatie with the release team to get a fix out. Since the
>>>>> maintainer is me and I'm already notified, please just point me at the
>>>>> commit fixing this bug, and I'll do the rest. Feel free to ping me if
>>>>> I take too long (I should be able to do it around the weekend, maybe
>>>>> even earlier).
>>>>>
>>>>> --
>>>>>
>>>>> Saludos,
>>>>> Felipe Sateler
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Live Security Virtual Conference
>>>>> Exclusive live event will cover all the ways today's security and
>>>>> threat landscape has changed and how IT managers can respond. Discussions
>>>>> will include endpoint security, mobile security and the latest in malware
>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>>> _______________________________________________
>>>>> Csound-devel mailing list
>>>>> Csound-devel@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond. Discussions
>>>> will include endpoint security, mobile security and the latest in malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |