You can intermix standard HTML and SB CGI files within your project. Only files referenced in the virtual directory structure (basic.conf) are processed by the sbhttpd proxy application server.

If you're using the Android Terminal app,  I think you should be able to create a directory via adb called /data/local/bin on a non-rooted device.  Then use adb to copy scriba there, and when you launch the Terminal app, scriba will be in the path that the app sets up.

I've managed to embed scriba within the Term.apk file itself, but it needs to be extracted from the apk so that the shell can find it, which I haven't worked out yet (building Win7 systems for a client this weekend.  Yuck.  sysprep to the rescue.)

A.

Updated Instructions

adb shell
mkdir /data/local/bin
exit
adb push scriba /data/local/bin/
adb push hello4.bas /sdcard

adb shell
cd /data/local/bin
ls -l (check permissions)

if needed, chmod 755 scriba

Then in Term app: scriba /sdcard/hello4.bas


Thanks for the patch and welcome to the ScriptBasic project.

I wanted to see if SB would work under OSX Lion, and ran into a bunch of issues getting it to compile.  I wasn't able to work those out fully, so instead I compiled it under Snow Leopard.  Note that for maximum compatibility, I compiled it for 32bit.

One of the things that's always bugged me about SB's "installer" is the fact that by default the System bin and lib folders are used.  For any add-on, /usr/local should be used.  So I reconfigured SB to do just that.

One thing you will find is that without a proper installer, most Mac users won't bother trying it out.  Since I had to test a new package installer program for work, I decided to create a proper Mac installer for SB.  I placed the installer within a DMG file, which is like an ISO under other OS's, which Macs can mount directly with a double-click.

The installed folder structure looks like this:

Code: [Select]

/usr/local
   --bin
     --scriba
     --sbhttpd
  --lib
    --scriba
  --share
    --scriba
      --examples
      --include
      --source
      --Script Basic User Guide.pdf

/etc
  --scriba
    --basic.conf


Screen Shots











DOWNLOAD

I hope to get BUILD 11 out this weekend for Linux (32/64) and Windows 32.

You could create a VirtualBox on your Windows PC and run Ubuntu 32 in it for testing and experimentation. Ubuntu has a dual boot option that uses a portion of your NTFS Windows file system so you don't need to partition your disk. If your PC is new enough and can boot off a USB drive, that is another great way to run Linux as a secondary OS.

Make sure you copy the libscriba.a and libscriba.so to your /usr/lib directory. That is were -lscriba is pointing to. This is your runtime library for your C wrapped script.

warning: no newline at end of file

This is only a compiler warning and doesn't need to be fixed to compile the program.

Advice

If your only creating one standalone SB executable script, it's faster to use the following method. (no compiling needed)

/usr/bin/scriba -Eo updater updater.sb

This appends the compiled (PCODE) to the end of scriba giving it the name your chose. Scriba always checks first if there is a script attached before processing any command line options.

The -C option is a better choice if you have a bunch of scripts that make up your application and using a common runtime shared object makes more sense. Scripts compiled to C normally have 12K of interface overhead and the rest is C wrapped PCODE. This option also allows you to link static to external libraries rather then having to distribute shared objects.

Please post the relevant code you are using to communicate with the serial port.

I haven't tried using SB with a serial port before but I see no reason it shouldn't work.

This works even though it isn't a tty serial port in the true sense.

OPEN "/dev/tty" FOR OUTPUT AS 1

PRINT #1,"Test\n"
LINE INPUT #1, i
PRINT i

jrs@laptop:~/sb/test$ scriba ttytest.sb
Test
jrs@laptop:~/sb/test$

Try "1*21999\r\n"

\r = RETURN
\n = LINEFEED