liblo-devel Mailing List for LibLO

On Mon, Aug 10, 2009 at 11:48 PM, Felipe Sateler<fsa...@gm...> wrote:
> El martes 4 de agosto, Stephen Sinclair escribió:
>> On Tue, Aug 4, 2009 at 1:41 AM, Felipe Sateler<fsa...@gm...> wrote:
>> > Hi. I'm the new maintainer (actually, part of a team) for liblo in
>> > debian, and I have been preparing the latest release for distribution for
>> > a while now. I want to ask what is the premake4 windows binary and lua
>> > script are, and why are they included (without source) in the source
>> > distribution. In debian we might be forced to remove the binary (as it is
>> > sourceless) from the source tarball, but this probably doesn't really
>> > matter much. I googled around and premake seems to be a build helper
>> > tool. If so, is its usage recommended? So far, we use the configure
>> > script + make to build liblo.
>>
>> Hi,
>>
>> Great to hear from you.  I'm very happy that debian is considering
>> including a newer version of liblo. The premake4 binary is in the
>> repo only for generating Visual Studio project files, and can safely
>> be ignored or removed on *nix.  I included it as a binary for
>> simplicity, it is unmodified from the premake project.  I took a cue
>> from the Open Dynamics Engine on using premake to handle Visual
>> Studio-related things, even the premake script file is modified from
>> their project.  The autotools build is still used for Linux, OS X, and
>> other *nix OSes.
>
> OK. FWIW, it would be simpler for me if you didn't ship the binary, because
> then I have to repack the tarball without it. It is not a big deal, however,
> as I already have a script in place to do this automatically.
>
>>
>> By the way, now that liblo includes a couple of tools (oscsend and
>> oscdump), you might consider creating a liblo-tools package, but
>> that's up to you obviously.  My 2cents is that I think it would be
>> incredibly useful if these command-line tools for sending and
>> receiving OSC could be included in Debian.
>>
>> (I already use these tools for doing unit testing on OSC-related
>> projects, for example.)
>
> Noted, the new version will include a liblo-tools package with said tools.


Great, thank you for your work!  That's excellent news.


Steve

El martes 4 de agosto, Stephen Sinclair escribió:
> On Tue, Aug 4, 2009 at 1:41 AM, Felipe Sateler<fsa...@gm...> wrote:
> > Hi. I'm the new maintainer (actually, part of a team) for liblo in
> > debian, and I have been preparing the latest release for distribution for
> > a while now. I want to ask what is the premake4 windows binary and lua
> > script are, and why are they included (without source) in the source
> > distribution. In debian we might be forced to remove the binary (as it is
> > sourceless) from the source tarball, but this probably doesn't really
> > matter much. I googled around and premake seems to be a build helper
> > tool. If so, is its usage recommended? So far, we use the configure
> > script + make to build liblo.
>
> Hi,
>
> Great to hear from you.  I'm very happy that debian is considering
> including a newer version of liblo. The premake4 binary is in the
> repo only for generating Visual Studio project files, and can safely
> be ignored or removed on *nix.  I included it as a binary for
> simplicity, it is unmodified from the premake project.  I took a cue
> from the Open Dynamics Engine on using premake to handle Visual
> Studio-related things, even the premake script file is modified from
> their project.  The autotools build is still used for Linux, OS X, and
> other *nix OSes.

OK. FWIW, it would be simpler for me if you didn't ship the binary, because 
then I have to repack the tarball without it. It is not a big deal, however, 
as I already have a script in place to do this automatically.

>
> By the way, now that liblo includes a couple of tools (oscsend and
> oscdump), you might consider creating a liblo-tools package, but
> that's up to you obviously.  My 2cents is that I think it would be
> incredibly useful if these command-line tools for sending and
> receiving OSC could be included in Debian.
>
> (I already use these tools for doing unit testing on OSC-related
> projects, for example.)

Noted, the new version will include a liblo-tools package with said tools.


Saludos,
Felipe Sateler

On Tue, Aug 4, 2009 at 1:41 AM, Felipe Sateler<fsa...@gm...> wrote:
> Hi. I'm the new maintainer (actually, part of a team) for liblo in debian, and
> I have been preparing the latest release for distribution for a while now. I
> want to ask what is the premake4 windows binary and lua script are, and why
> are they included (without source) in the source distribution. In debian we
> might be forced to remove the binary (as it is sourceless) from the source
> tarball, but this probably doesn't really matter much. I googled around and
> premake seems to be a build helper tool. If so, is its usage recommended? So
> far, we use the configure script + make to build liblo.

Hi,

Great to hear from you.  I'm very happy that debian is considering
including a newer version of liblo.  The premake4 binary is in the
repo only for generating Visual Studio project files, and can safely
be ignored or removed on *nix.  I included it as a binary for
simplicity, it is unmodified from the premake project.  I took a cue
from the Open Dynamics Engine on using premake to handle Visual
Studio-related things, even the premake script file is modified from
their project.  The autotools build is still used for Linux, OS X, and
other *nix OSes.

By the way, now that liblo includes a couple of tools (oscsend and
oscdump), you might consider creating a liblo-tools package, but
that's up to you obviously.  My 2cents is that I think it would be
incredibly useful if these command-line tools for sending and
receiving OSC could be included in Debian.

(I already use these tools for doing unit testing on OSC-related
projects, for example.)


Steve

Hi. I'm the new maintainer (actually, part of a team) for liblo in debian, and 
I have been preparing the latest release for distribution for a while now. I 
want to ask what is the premake4 windows binary and lua script are, and why 
are they included (without source) in the source distribution. In debian we 
might be forced to remove the binary (as it is sourceless) from the source 
tarball, but this probably doesn't really matter much. I googled around and 
premake seems to be a build helper tool. If so, is its usage recommended? So 
far, we use the configure script + make to build liblo.

Saludos,
Felipe Sateler