tiko freebasic compatibility best practice

[ron77]

hi

i apologize for the silly question -

in order to have tiko compile my old freebasic code that uses libraries such as bass lib squlite3 lib window9 gui lib libvt (made a special version that is compatible for both fb and tiko) and so on...

in order for tiko to compile my fb code i usually copy headers from my freebasic include/ subfolder into tiko inc/ subfolder i make sure that the copying skip files and headers that are already there with same names - that's how i am able to compile with tiko using fb libs

my question is is this good practice? i know tiko is suppose to be fb compatible but if so am what i'm doing is a good habit or should i just stop doing it and just use the headers and libs that tiko brings with itself?

ron77

[Paul Squires]

There is absolutely nothing wrong with using the #Include approach.

Once your app is working with #Include, you can then experiment with things like #Import, #foreignlib, etc.

Tiko is compatible with #lang "fb" so porting from FB should be mostly trouble free.

[ron77]

another dumb question...

just tiko compile and run sdl3 audio wav example but i wonder how tiko managed to compile and run it without a header .bi for sdl3 (i installed sdl3 with 'sudo apt install libsdl3-dev') is tiko able to use c headers and libraries without a tiko header?

sorry for the silly question - i should really read the tiko book

ron77

[Paul Squires]

SDL3 is a built in package in tiko.

Take a look at the "pkg" folder (short for "packages"). In there you'll find several sub folders. "std" is the standard library files; "sys" contains system files, most notably the "win" or Windows files (José is maintaining this collection); and finally "vendor" where some 3rd party packages reside like SDL3, Raylib, Sqlite, etc.

In tiko, you simply need to "#import" the package you need.

Yes, read the tiko book and browse through the tiko by-example book also. If you make it through all of that then you'll be a tiko superstar. 

[Paul Squires]

...and also yes, tiko can use most C headers directly via the #cinclude statement. The tiko wiki has a full tutorial on using raw C headers directly with tiko.