Menu
▾
▴
liblo-devel — Discussion of liblo library and application development
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(3) |
Jul
|
Aug
(7) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(7) |
| 2006 |
Jan
(1) |
Feb
(2) |
Mar
(3) |
Apr
(3) |
May
(5) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(4) |
Oct
(17) |
Nov
(18) |
Dec
(1) |
| 2007 |
Jan
|
Feb
|
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(6) |
Dec
(1) |
| 2008 |
Jan
(17) |
Feb
(20) |
Mar
(8) |
Apr
(8) |
May
(10) |
Jun
(4) |
Jul
(5) |
Aug
(6) |
Sep
(9) |
Oct
(19) |
Nov
(4) |
Dec
(35) |
| 2009 |
Jan
(40) |
Feb
(16) |
Mar
(7) |
Apr
(6) |
May
|
Jun
(5) |
Jul
(5) |
Aug
(4) |
Sep
(1) |
Oct
(2) |
Nov
(15) |
Dec
(15) |
| 2010 |
Jan
(5) |
Feb
(20) |
Mar
(12) |
Apr
|
May
(2) |
Jun
(4) |
Jul
|
Aug
(11) |
Sep
(1) |
Oct
(1) |
Nov
(3) |
Dec
|
| 2011 |
Jan
(8) |
Feb
(19) |
Mar
|
Apr
(12) |
May
(7) |
Jun
(8) |
Jul
|
Aug
(1) |
Sep
(21) |
Oct
(7) |
Nov
(4) |
Dec
|
| 2012 |
Jan
(3) |
Feb
(25) |
Mar
(8) |
Apr
(10) |
May
|
Jun
(14) |
Jul
(5) |
Aug
(12) |
Sep
(3) |
Oct
(14) |
Nov
|
Dec
|
| 2013 |
Jan
(10) |
Feb
(4) |
Mar
(10) |
Apr
(14) |
May
(6) |
Jun
(13) |
Jul
(37) |
Aug
(20) |
Sep
(11) |
Oct
(1) |
Nov
(34) |
Dec
|
| 2014 |
Jan
(8) |
Feb
(26) |
Mar
(24) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(28) |
Oct
(4) |
Nov
(4) |
Dec
(2) |
| 2015 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(13) |
Jul
|
Aug
(3) |
Sep
(8) |
Oct
(11) |
Nov
(16) |
Dec
|
| 2016 |
Jan
|
Feb
(6) |
Mar
|
Apr
(9) |
May
(23) |
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
(3) |
Jun
|
Jul
(3) |
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
(3) |
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(31) |
May
|
Jun
|
Jul
|
Aug
(7) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2021 |
Jan
(2) |
Feb
(2) |
Mar
(5) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
|
2
|
3
|
4
|
5
|
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
|
20
|
21
|
22
|
23
|
24
|
25
(1) |
26
|
|
27
|
28
(2) |
29
(1) |
30
|
31
|
|
|
|
From: Stephen S. <rad...@gm...> - 2019-01-29 16:42:47
|
configure takes an argument --enable-threads, which should be on by default but can be disabled. This sets an automake variable ENABLE_THREADS which only compiles server_threads.c if enabled. It also defines HAVE_LIBPTHREAD (unless you enable win32 threads by a similar manner, defining HAVE_WIN32_THREADS). If you used premake4 for Windows, then you can supply --without-threads which will have similar effect. (Actually the README in build seems out of date, as it claims that win32 threads are not supported, which has since been added.) Similarly the CMake build provides an option called THREADING that has similar effect. If server_threads.c was not included in the build then the symbols lo_server_thread_new etc will not be available. Note that during build, lo.h is generated from lo.h.in, where the line #include "lo/lo_serverthread.h" is added to lo.h or not, depending on the configuration as I just described. That means that if you are #including the generated lo.h, you should see a compilation error rather than the linking error like you indicate. So make sure your lo.h corresponds with the binary you are linking to. regards, Steve On Mon, Jan 28, 2019 at 1:01 PM Eric Black <eri...@gm...> wrote: > > I didn't see anything that ties up to this. How can I enable them? > > Stephen Sinclair <rad...@gm...> ezt írta (időpont: 2019. jan. 28., H, 12:50): >> >> Did you build liblo with threads enabled? >> >> Steve >> >> On Fri, Jan 25, 2019 at 5:46 PM Eric Black <eri...@gm...> wrote: >> > >> > Good afternoon, >> > We're working on to make Sonic Visualiser be able to have liblo integrated in it but it always give us unresolved external error messages. (VS2017) >> > >> > Do you have any idea? >> > >> > >> > "C:\SAGAX\sonic_source\sonic-visualiser\build_win64\sonic-visualiser.sln" (Build target) (1) -> >> > "C:/SAGAX/sonic_source/sonic-visualiser/build_win64\Sonic Visualiser.vcxproj.metaproj" (default target) (18) -> >> > "C:\SAGAX\sonic_source\sonic-visualiser\build_win64\Sonic Visualiser.vcxproj" (default target) (19) -> >> > (Link target) -> >> > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_new [C:\SAGAX\sonic_source\sonic- >> > visualiser\build_win64\Sonic Visualiser.vcxproj] >> > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_add_method [C:\SAGAX\sonic_source >> > \sonic-visualiser\build_win64\Sonic Visualiser.vcxproj] >> > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_start [C:\SAGAX\sonic_source\soni >> > c-visualiser\build_win64\Sonic Visualiser.vcxproj] >> > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_stop [C:\SAGAX\sonic_source\sonic >> > -visualiser\build_win64\Sonic Visualiser.vcxproj] >> > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_get_url [C:\SAGAX\sonic_source\so >> > nic-visualiser\build_win64\Sonic Visualiser.vcxproj] >> > release\\Sonic Visualiser.exe : fatal error LNK1120: 5 unresolved externals [C:\SAGAX\sonic_source\sonic-visualiser\b >> > uild_win64\Sonic Visualiser.vcxproj] >> > >> > 395 Warning(s) >> > 6 Error(s) >> > _______________________________________________ >> > liblo-devel mailing list >> > lib...@li... >> > https://lists.sourceforge.net/lists/listinfo/liblo-devel >> >> >> _______________________________________________ >> liblo-devel mailing list >> lib...@li... >> https://lists.sourceforge.net/lists/listinfo/liblo-devel > > _______________________________________________ > liblo-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/liblo-devel |
|
From: Eric B. <eri...@gm...> - 2019-01-28 12:01:40
|
I didn't see anything that ties up to this. How can I enable them? Stephen Sinclair <rad...@gm...> ezt írta (időpont: 2019. jan. 28., H, 12:50): > Did you build liblo with threads enabled? > > Steve > > On Fri, Jan 25, 2019 at 5:46 PM Eric Black <eri...@gm...> > wrote: > > > > Good afternoon, > > We're working on to make Sonic Visualiser be able to have liblo > integrated in it but it always give us unresolved external error messages. > (VS2017) > > > > Do you have any idea? > > > > > > > "C:\SAGAX\sonic_source\sonic-visualiser\build_win64\sonic-visualiser.sln" > (Build target) (1) -> > > "C:/SAGAX/sonic_source/sonic-visualiser/build_win64\Sonic > Visualiser.vcxproj.metaproj" (default target) (18) -> > > "C:\SAGAX\sonic_source\sonic-visualiser\build_win64\Sonic > Visualiser.vcxproj" (default target) (19) -> > > (Link target) -> > > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol > lo_server_thread_new [C:\SAGAX\sonic_source\sonic- > > visualiser\build_win64\Sonic Visualiser.vcxproj] > > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol > lo_server_thread_add_method [C:\SAGAX\sonic_source > > \sonic-visualiser\build_win64\Sonic Visualiser.vcxproj] > > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol > lo_server_thread_start [C:\SAGAX\sonic_source\soni > > c-visualiser\build_win64\Sonic Visualiser.vcxproj] > > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol > lo_server_thread_stop [C:\SAGAX\sonic_source\sonic > > -visualiser\build_win64\Sonic Visualiser.vcxproj] > > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol > lo_server_thread_get_url [C:\SAGAX\sonic_source\so > > nic-visualiser\build_win64\Sonic Visualiser.vcxproj] > > release\\Sonic Visualiser.exe : fatal error LNK1120: 5 unresolved > externals [C:\SAGAX\sonic_source\sonic-visualiser\b > > uild_win64\Sonic Visualiser.vcxproj] > > > > 395 Warning(s) > > 6 Error(s) > > _______________________________________________ > > liblo-devel mailing list > > lib...@li... > > https://lists.sourceforge.net/lists/listinfo/liblo-devel > > > _______________________________________________ > liblo-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/liblo-devel > |
|
From: Stephen S. <rad...@gm...> - 2019-01-28 11:50:08
|
Did you build liblo with threads enabled? Steve On Fri, Jan 25, 2019 at 5:46 PM Eric Black <eri...@gm...> wrote: > > Good afternoon, > We're working on to make Sonic Visualiser be able to have liblo integrated in it but it always give us unresolved external error messages. (VS2017) > > Do you have any idea? > > > "C:\SAGAX\sonic_source\sonic-visualiser\build_win64\sonic-visualiser.sln" (Build target) (1) -> > "C:/SAGAX/sonic_source/sonic-visualiser/build_win64\Sonic Visualiser.vcxproj.metaproj" (default target) (18) -> > "C:\SAGAX\sonic_source\sonic-visualiser\build_win64\Sonic Visualiser.vcxproj" (default target) (19) -> > (Link target) -> > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_new [C:\SAGAX\sonic_source\sonic- > visualiser\build_win64\Sonic Visualiser.vcxproj] > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_add_method [C:\SAGAX\sonic_source > \sonic-visualiser\build_win64\Sonic Visualiser.vcxproj] > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_start [C:\SAGAX\sonic_source\soni > c-visualiser\build_win64\Sonic Visualiser.vcxproj] > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_stop [C:\SAGAX\sonic_source\sonic > -visualiser\build_win64\Sonic Visualiser.vcxproj] > base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol lo_server_thread_get_url [C:\SAGAX\sonic_source\so > nic-visualiser\build_win64\Sonic Visualiser.vcxproj] > release\\Sonic Visualiser.exe : fatal error LNK1120: 5 unresolved externals [C:\SAGAX\sonic_source\sonic-visualiser\b > uild_win64\Sonic Visualiser.vcxproj] > > 395 Warning(s) > 6 Error(s) > _______________________________________________ > liblo-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/liblo-devel |
|
From: Eric B. <eri...@gm...> - 2019-01-25 16:46:43
|
Good afternoon,
We're working on to make Sonic Visualiser be able to have liblo integrated
in it but it always give us unresolved external error messages. (VS2017)
Do you have any idea?
"C:\SAGAX\sonic_source\sonic-visualiser\build_win64\sonic-visualiser.sln"
(Build target) (1) ->
"C:/SAGAX/sonic_source/sonic-visualiser/build_win64\Sonic
Visualiser.vcxproj.metaproj" (default target) (18) ->
"C:\SAGAX\sonic_source\sonic-visualiser\build_win64\Sonic
Visualiser.vcxproj" (default target) (19) ->
(Link target) ->
base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol
lo_server_thread_new [C:\SAGAX\sonic_source\sonic-
visualiser\build_win64\Sonic Visualiser.vcxproj]
base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol
lo_server_thread_add_method [C:\SAGAX\sonic_source
\sonic-visualiser\build_win64\Sonic Visualiser.vcxproj]
base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol
lo_server_thread_start [C:\SAGAX\sonic_source\soni
c-visualiser\build_win64\Sonic Visualiser.vcxproj]
base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol
lo_server_thread_stop [C:\SAGAX\sonic_source\sonic
-visualiser\build_win64\Sonic Visualiser.vcxproj]
base.lib(OSCQueue.obj) : error LNK2001: unresolved external symbol
lo_server_thread_get_url [C:\SAGAX\sonic_source\so
nic-visualiser\build_win64\Sonic Visualiser.vcxproj]
release\\Sonic Visualiser.exe : fatal error LNK1120: 5 unresolved
externals [C:\SAGAX\sonic_source\sonic-visualiser\b
uild_win64\Sonic Visualiser.vcxproj]
395 Warning(s)
6 Error(s)
|