bwbasic

[KernelKarter]

I've got hold of a openSUSE SRPM (with the patches) and after a lot of fiddling around with the spec file, I've managed to build a package without the patches. I haven't a clue what the patches are or do and my tweaked spec file doesn't look right but my package builds and appears to install correctly.

TTFN,
KK

[rich2005]

Also, it wasn't happy with a  '60 print "output= " output' which I think ought to work, so I have to figure out why not. (Maybe a typo.)

Pleased you got it working, I use yabasic - much of a muchness.

Your syntax error, you need a comma between the string and the variable as

http://i.imgur.com/9ROxP.jpg

[KernelKarter]

The Makefile will instruct is to install in /usr/local/bin, which is appropriate if /usr/local/bin is in your path. If not, you have to add it to your path or change the Makefile to say "prefix=/usr". Normally, this is passed with "./configure --prefix=/usr", but this doesn't seem to work with this program.

Hmmmmm, --prefix=/usr works just fine here. How strange 

TTFN,
KK

[gseaman]

The Makefile will instruct is to install in /usr/local/bin, which is appropriate if /usr/local/bin is in your path. If not, you have to add it to your path or change the Makefile to say "prefix=/usr". Normally, this is passed with "./configure --prefix=/usr", but this doesn't seem to work with this program.

Hmmmmm, --prefix=/usr works just fine here. How strange 

TTFN,
KK

That is strange. I ran ./configure --prefix=/usr. The command ran just fine, but the Makefile still said /usr/local/bin.

Galen

[KernelKarter]

The Makefile will instruct is to install in /usr/local/bin, which is appropriate if /usr/local/bin is in your path. If not, you have to add it to your path or change the Makefile to say "prefix=/usr". Normally, this is passed with "./configure --prefix=/usr", but this doesn't seem to work with this program.

Hmmmmm, --prefix=/usr works just fine here. How strange 

TTFN,
KK

That is strange. I ran ./configure --prefix=/usr. The command ran just fine, but the Makefile still said /usr/local/bin.

Galen

Well yes, that is strange <scratches head>.

Here's a snippet from my Makefile:

Code: [Select]

prefix = /usr
exec_prefix = /usr
bindir = $(exec_prefix)/bin

Incidentally, after a bit more tweaking on the spec file, I've managed to build the package. However, as I'm a n00b as far as packaging is concerned, I'm doing this as part of my learning process and enjoying every minute of it. I have a RPM and a SRPM and the package appears to be OK as it installs correctly and I can see it in Synaptic with all the correct info displayed.

TTFN,
KK

[dougmack]

To: rich2005
Thanx, Rich.  I found that out--I read the .doc file and discovered my error.  For all I remember, the "original" GWBASIC had the same thing--it's
been a while.  Since you are familiar with this, perhaps you can tell me what I need to do to make lprint output to lpr.  Most of the s/w from
long ago does output to the printer when run in DOS.  I tried a number of things based on the info in the .doc file, but couldn't find the sweet
spot.   TIA--doug

[AS]

In available docs LPRINT is listed under "unimplemented commands" chapter:
http://www.bwbasic.at/info.htm

It it's me, I would direct all output to to a text files, say $OUTFILE="/tmp/out.txt",
and at end of work, you can call something like "system("lpr " & $OUTFILE)

(not sure about syntax, never used bwbasic or gwbasic, still I have used others old BASIC languages)

AS

[rich2005]

@dougmack

You caught me now. As previous post I dont think you will get one of these small basics to print in linux (someone bound to prove me wrong). Yabasic will dump a graphics screen to a postscript file, for text best I can suggest is to "print" to a file

Just checked the bwbasic syntax, it is a little different to yabasic, and was nagging a bit. OUTPUT is a bw/gw basic keyword  and really should not be used as a variable even in lowercase.

so in bwbasic this should work, the file test.txt will be created.

OPEN "test.txt" FOR OUTPUT AS #1
first = 30
second = 20
result = first*second
PRINT #1 "result = " , result
CLOSE #1

as a note, yabasic compiles really easily to a single file.
for something a bit more ambitious, freebasic works ootb and integrates well with geany, although it has some annoying aspects lprint should work. maybe a candidate for a .rpm

[dougmack]

Thanx, folks. I didn't really use the word "output" in my test, I just wrote it in my example, not realizing that it was a reserved word.

I've heard of freebasic, but it's not in the repo.  Should I try and get it?  I only need one, and it should be as near to GWBASIC as possible.
I really don't care if you can compile it.  Nothing I have seen is big enough to be worth compiling, and it's certainly faster to troubleshoot
if you don't.

--doug

[rich2005]

FreeBasic 'aims' to be compatible with QuickBasic and as such will build and compile nice little executables. Easy to install as the installer just copies files around and uninstalls as well.

But for your purposes not compatible with GWBasic so stick with bwbasic.

Which puts me in reminising mode.

In the 1980's there was a "clone" of GWbasic I think it was called Prado-Basic, hailed as good as GWbasic, you could download from bulletin boards, lots of the shareware people would include it on software disks.
So good because it was GWBasic, hacked to remove the credits which were replaced with
"If you find this useful send $10 to......." 
Good Scam.

[dougmack]

I hadn't heard of that. I love it!   -doug