liblo-devel Mailing List for LibLO

We are pleased to present stable release 0.28 of LibLo, the
lightweight, easy to use implementation of the Open Sound Control
protocol.

It can be downloaded from:

https://downloads.sourceforge.net/project/liblo/liblo/0.28/liblo-0.28.tar.gz

The project home page can be found at:

http://liblo.sf.net

Open Sound Control (OSC) is a protocol for communication among
computers, sound synthesizers, and other multimedia devices that is
designed for use over modern network transports.

Changes since the 0.28rc release candidate include:

- Fixed build for Windows (MingW, MSVC) and Android platforms
- Fixed an implicit cast issue in C++ bindings for lo::ServerThread
- Documentation, small fixes
- Added a function to get library version information (lo_version)

Additionally, since the last release candidate included the following
improvements over version 0.27:

Important bug fixes:

- Fixed checking of vararg markers on 64-bit systems
- Fixed hang in TCP blocking test
- Several potential bugs prevented through static analysis

Additional changes:

- Add function lo_bundle_get_timestamp()
- Add C++11 wrapper, `lo_cpp.h', and test program
- Support for a few more build tools: clang/clang++, ccache

Enjoy, and please report any issues to the liblo mailing list.

thank you,

Steve Sinclair
(liblo maintainer)

Great!

Yes, if maintainer-mode is not enabled then changes in Makefile.am and
configure.ac will not be autodetected by make.

Thanks for the report.

cheers,
Steve


On Tue, Jan 21, 2014 at 2:48 PM, Felipe Sateler <fsa...@gm...> wrote:
> On Tue, Jan 21, 2014 at 10:25 AM, Stephen Sinclair <rad...@gm...> wrote:
>> Did you re-run configure, or autogen.sh?  I added this function,
>> lo_version, in d302f29.  There should be a file, src/version.c, where
>> it is defined.
>
> Ah, yes. configure is not enough, autogen.sh is needed. Thanks.
>
> BTW, doxygen emits a warning:
> Warning: Tag `SYMBOL_CACHE_SIZE' at line 336 of file reference.doxygen
> has become obsolete.
>
> Testlo is running correctly here.
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel

On Tue, Jan 21, 2014 at 10:25 AM, Stephen Sinclair <rad...@gm...> wrote:
> Did you re-run configure, or autogen.sh?  I added this function,
> lo_version, in d302f29.  There should be a file, src/version.c, where
> it is defined.

Ah, yes. configure is not enough, autogen.sh is needed. Thanks.

BTW, doxygen emits a warning:
Warning: Tag `SYMBOL_CACHE_SIZE' at line 336 of file reference.doxygen
has become obsolete.

Testlo is running correctly here.


-- 

Saludos,
Felipe Sateler

Did you re-run configure, or autogen.sh?  I added this function,
lo_version, in d302f29.  There should be a file, src/version.c, where
it is defined.

Actually, this is a version I've been meaning to add for some time, if
anyone has comments on the prototype or implementation please feel
free.

Steve


On Tue, Jan 21, 2014 at 2:13 PM, Felipe Sateler <fsa...@gm...> wrote:
> I'm getting a build failure:
>
> /bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -I.. -g -O2
> -o testlo testlo-testlo.o liblo.la -lpthread -lm
> libtool: link: gcc -Wall -I.. -g -O2 -o .libs/testlo testlo-testlo.o
> ./.libs/liblo.so -lpthread -lm
> testlo-testlo.o: In function `test_version':
> /home/felipe/src/deb/liblo/upstream/src/testlo.c:1046: undefined
> reference to `lo_version'
> collect2: error: ld returned 1 exit status
>
>
> This is debian 64bit
>
>
> On Tue, Jan 21, 2014 at 9:42 AM, Stephen Sinclair <rad...@gm...> wrote:
>> Hi Camille,
>>
>> Thanks for checking up.  Yes, I think it's looking pretty good now.
>> Most of my fixes lately have been getting it working on Windows.
>>
>> Steve
>>
>>
>> On Tue, Jan 21, 2014 at 9:18 AM, Camille Troillard
>> <ca...@os...> wrote:
>>> I have tested the latest commit on OS X, so far so good.
>>> Thanks Stephen!
>>>
>>>
>>>> On 14 janv. 2014, at 17:11, Stephen Sinclair <rad...@gm...> wrote:
>>>>
>>>> I think enough time has passed and we have fixed and reported many
>>>> bugs since 0.28rc.  I've tested on Linux 32/64-bit, Mac, and WIndows.
>>>>
>>>> Finally got testlo to pass on Windows. (Albeit a very old Windows XP
>>>> machine, 32-bit tested only.)  The main issue was that it was not
>>>> executing subtest properly, I replaced the 'system' call with 'spawnl'
>>>> on Windows which seemed to work, as long as it gets the absolute path
>>>> to subtest.exe.
>>>>
>>>> So I am more confident now that any show stoppers are ironed out, and
>>>> I will prepare 0.28 for release very soon.  Please report any
>>>> last-minute issues.
>>>
>>> ------------------------------------------------------------------------------
>>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>>> Critical Workloads, Development Environments & Everything In Between.
>>> Get a Quote or Start a Free Trial Today.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> liblo-devel mailing list
>>> lib...@li...
>>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>>
>> ------------------------------------------------------------------------------
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
>
>
> --
>
> Saludos,
> Felipe Sateler
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel

I'm getting a build failure:

/bin/bash ../libtool  --tag=CC   --mode=link gcc -Wall -I.. -g -O2
-o testlo testlo-testlo.o liblo.la -lpthread -lm
libtool: link: gcc -Wall -I.. -g -O2 -o .libs/testlo testlo-testlo.o
./.libs/liblo.so -lpthread -lm
testlo-testlo.o: In function `test_version':
/home/felipe/src/deb/liblo/upstream/src/testlo.c:1046: undefined
reference to `lo_version'
collect2: error: ld returned 1 exit status


This is debian 64bit


On Tue, Jan 21, 2014 at 9:42 AM, Stephen Sinclair <rad...@gm...> wrote:
> Hi Camille,
>
> Thanks for checking up.  Yes, I think it's looking pretty good now.
> Most of my fixes lately have been getting it working on Windows.
>
> Steve
>
>
> On Tue, Jan 21, 2014 at 9:18 AM, Camille Troillard
> <ca...@os...> wrote:
>> I have tested the latest commit on OS X, so far so good.
>> Thanks Stephen!
>>
>>
>>> On 14 janv. 2014, at 17:11, Stephen Sinclair <rad...@gm...> wrote:
>>>
>>> I think enough time has passed and we have fixed and reported many
>>> bugs since 0.28rc.  I've tested on Linux 32/64-bit, Mac, and WIndows.
>>>
>>> Finally got testlo to pass on Windows. (Albeit a very old Windows XP
>>> machine, 32-bit tested only.)  The main issue was that it was not
>>> executing subtest properly, I replaced the 'system' call with 'spawnl'
>>> on Windows which seemed to work, as long as it gets the absolute path
>>> to subtest.exe.
>>>
>>> So I am more confident now that any show stoppers are ironed out, and
>>> I will prepare 0.28 for release very soon.  Please report any
>>> last-minute issues.
>>
>> ------------------------------------------------------------------------------
>> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
>> Learn Why More Businesses Are Choosing CenturyLink Cloud For
>> Critical Workloads, Development Environments & Everything In Between.
>> Get a Quote or Start a Free Trial Today.
>> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>> _______________________________________________
>> liblo-devel mailing list
>> lib...@li...
>> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel



-- 

Saludos,
Felipe Sateler

Hi Camille,

Thanks for checking up.  Yes, I think it's looking pretty good now.
Most of my fixes lately have been getting it working on Windows.

Steve


On Tue, Jan 21, 2014 at 9:18 AM, Camille Troillard
<ca...@os...> wrote:
> I have tested the latest commit on OS X, so far so good.
> Thanks Stephen!
>
>
>> On 14 janv. 2014, at 17:11, Stephen Sinclair <rad...@gm...> wrote:
>>
>> I think enough time has passed and we have fixed and reported many
>> bugs since 0.28rc.  I've tested on Linux 32/64-bit, Mac, and WIndows.
>>
>> Finally got testlo to pass on Windows. (Albeit a very old Windows XP
>> machine, 32-bit tested only.)  The main issue was that it was not
>> executing subtest properly, I replaced the 'system' call with 'spawnl'
>> on Windows which seemed to work, as long as it gets the absolute path
>> to subtest.exe.
>>
>> So I am more confident now that any show stoppers are ironed out, and
>> I will prepare 0.28 for release very soon.  Please report any
>> last-minute issues.
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel

I have tested the latest commit on OS X, so far so good.
Thanks Stephen!


> On 14 janv. 2014, at 17:11, Stephen Sinclair <rad...@gm...> wrote:
> 
> I think enough time has passed and we have fixed and reported many
> bugs since 0.28rc.  I've tested on Linux 32/64-bit, Mac, and WIndows.
> 
> Finally got testlo to pass on Windows. (Albeit a very old Windows XP
> machine, 32-bit tested only.)  The main issue was that it was not
> executing subtest properly, I replaced the 'system' call with 'spawnl'
> on Windows which seemed to work, as long as it gets the absolute path
> to subtest.exe.
> 
> So I am more confident now that any show stoppers are ironed out, and
> I will prepare 0.28 for release very soon.  Please report any
> last-minute issues.

Hello folks,

I think enough time has passed and we have fixed and reported many
bugs since 0.28rc.  I've tested on Linux 32/64-bit, Mac, and WIndows.

Finally got testlo to pass on Windows. (Albeit a very old Windows XP
machine, 32-bit tested only.)  The main issue was that it was not
executing subtest properly, I replaced the 'system' call with 'spawnl'
on Windows which seemed to work, as long as it gets the absolute path
to subtest.exe.

So I am more confident now that any show stoppers are ironed out, and
I will prepare 0.28 for release very soon.  Please report any
last-minute issues.

cheers,
Steve