Getting VBCC, Roadshow, and Posix to Play Together

[tygre]

Hi all!

So far, I have been compiling AmiModRadio against the Miami SDK just fine .

I'd like to replace the Miami SDK with the Roadshow one, which last version (?) I found here. Naively , I thought that it would be a simple matter of changing the compiler/linker options to point to the new SDK... Alas! I have the same problem as walkero-gr (see bottom of the page, although I'm not using AmiSSL): file 'inline/bsdsocket_protos.h' not found. I have also read this and that posts, but I'm still confused

Here are the options that I'm currently using:

-lmieee
-cpp-comments
-c99
-Idevkits:sdk/classic/MUI/Developer/C/Include/
-Idevkits:sdk/classic/MiamiSDK/netinclude/
-IDevKits:sdk/classic/xad/Include/C/
-IDevKits:compilers/vbcc/0.9g/posixlib/include/
-Lvbcc:posixlib/lib/
-Lvbcc:targets/m68k-amigaos/lib/
-lamiga
-lposix

Is it possible to have both Posix and Roadshow together with VBCC? Certainly... but what should I change?

Thanks in advance!

[phx]

PosixLib is meant for porting Unix sources more easily. AmiModRadio is an Amiga program, so I don't understand why there are any references to POSIX functions in it. You may take the chance to replace them by AmigaOS calls now, and then you already have one big problem less.

PosixLib and AmiTCP/Roadshow don't harmonize together very well. Therefore I added most network functions to PosixLib (sys/socket.h), which will open bsdsocket.library for you.

Regarding Roadshow I have to admit that I never saw the SDK before (thanks for the link!). Always thought that it is 100% compatible to AmiTCP. But it looks like the proto and clib headers are called "bsdsocket" instead of "socket".

I will make sure vbcc includes Roadshow support with the upcoming V0.9h release. For older versions you have to generate the inline (and proto?) header files yourself, like mentioned here: https://eab.abime.net/showpost.php?p...07&postcount=6

Using the SFD file from the Roadshow SDK this would be:

fd2pragma special 70 voidbase to path_to/inline RoadShow_SDK/sfd/bsdsocket_lib.sfd

[bebbo]

Originally Posted by phx

...


Regarding Roadshow I have to admit that I never saw the SDK before (thanks for the link!). Always thought that it is 100% compatible to AmiTCP. But it looks like the proto and clib headers are called "bsdsocket" instead of "socket".
...

Roadshow provides socket.h headers which include bsdsocket.h.


The SDK does not matter, at least for the resulting program. For the code there are some differences.

[phx]

Originally Posted by bebbo

Roadshow provides socket.h headers which include bsdsocket.h.

Indeed. And the base is still

SocketBase

. It was probably too late last night.

Then Tygre can include the existing

<proto/socket.h>

header and should be fine, as long as no Roadshow-specific functions are needed.

EDIT: Had a closer look on the Roadshow SDK this weekend, and the netinclude folder is missing most POSIX headers, like sys/types.h, unitstd.h, etc.. So this might have been the reason for PosixLib. Better use the AmiTCP SDK with vbcc.

[tygre]

Hi PHX and Bebbo!

Thank you so much for your answers, you were right and helped me a lot! I managed to create the bsdsocket_protos.h and compile AmiModRadio against Roadshow. I also remove (most) dependencies to the POSIX library.

(I still use some POSIX functions, out of sheer lazyness , like opendir(), readdir(), and scandir()... I will replace them with AmigaOS Examine and ExAll later )

The reason why I wanted to compile against Roadshow is that it allows declaring NOLIBBASE and replace a global SocketBase variable with a per-task SocketBase, thank you AROS developers! Thus, multiple tasks can open and use sockets like, for AmiModRadio, fetching a module while rating another one. Fetching and rating at the same time used to create problems (leading often to crashes), but not anymore! The real reason is, of course, that I should have RTFMed from the beginning: "The recommended approach, if several Processes need to use the "bsdsocket.library" functions, is to reopen the library for every user." (Autodocs on OpenLibrary).

Cheers!