[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [school-discuss] Installing From Tar



Joel:

I opened things up and found a few items in the tar file that might
explain why you would have problems building the program.

> more COMPILING.txt
Compiling Instructions and Dependencies
2014-04-18 VERSION 1.1.1.3

LINUX you will need:
* g++
* qt4-dev-tools
* flex
* bison
* libsdl-mixer??-dev
* libespeak-dev (if using the LINUX_ESPEAK option in BASIC256.pro)
  - this option gives an integrated library approach to the say statement
* espeak (if using the LINUX_ESPEAK_EXECUTE option in BASIC256.pro)
  - use this option and install if the library use of portaudio conflicts with other sound systems installed

However from:
> more Makefile
#############################################################################
# Makefile for building: basic256
# Generated by qmake (3.0) (Qt 5.2.1)
# Project:  BASIC256.pro
# Template: app
# Command: /usr/lib/x86_64-linux-gnu/qt5/bin/qmake -config debug -o Makefile BASIC256.pro
#############################################################################

and from:
> more BASIC256.pro
lessThan(QT_MAJOR_VERSION, 5) {
  message( FATAL_ERROR "BASIC-256 requires QT 5 or better." )
}

So - despite the reference in the main web page and the install instructions that this
works with Qt4, you can see in the make file that you will need at least Qt5 and since
it was made using Qt5.2.1, I would guess that anything less a Linux version with Qt5.2.1,
building it will fail or not run properly.

I checked distrowatch.com and found the Ubuntu 14.04LTS uses Qt5.2.1 and thus would be my
guess and suggestion for which distro you need to be running if you want to build from
tar this package. It also appears that it is the x86_64 version and thus you will have problems
building it on any i386 system. All the qmake files have x86_64 embedded in them and thus
the path to objects would be wrong on a i386 systems.

Hope that clears up some of your problems.
Bill.


On 12/21/2014 10:18 AM, kibler wrote:
Joel:

A few notes - your more information is for sure a help.
However you didn't really say much about the laptop other than it had
run Windows - was that XP? Many of the older XP laptops have unique
hardware and as such not all versions of Linux will support your
system - you may need a version for older hardware.

As to the compiling, I downloaded the tar file and from a quick
review - it seems to be for Ubuntu version 12 or 13, but it
doesn't actually say so. I noticed several missing compiler files
and tools, which on that alone suggest someone not use to making
programs for Unix/Linux systems is behind the project.

I will try and compile it later, but on first pass it seems you will
have considerable problems simply from the lack of developer
information and use of standard tools and processes. I have seen
this more often of late - people with limited knowledge releasing
packages that require considerably more skills than the
average user has to make them work.

Making it work for you is not impossible, just not going to be easy.
Bill.


On 12/21/2014 09:17 AM, Joel Kahn wrote:
Thanks for the responses.

David has a good point in his suggestion that I provide
specifics. Here's a bit of background.

As I've mentioned in this group before, I've been using a
GPL programming language....

http://basic256.org/index_en

....to produce digital art. BASIC-256 is available for
both MS Windows and Linux (in fact, I originally began
using it on a Windows machine). My primary computer
right now is a laptop on which the pre-loaded Windows
died; the Linux distros I've installed on it since have run
fairly well. I intend to keep doing most of my work with
BASIC-256 on this laptop until further notice.

Since BASIC-256 is a fairly obscure app, it's not available
for easy setup in every distro. In the ones where it does
appear, the file in the repository is not always the latest
version. Furthermore, some versions have demonstrated
a few bugs on my particular hardware. Support is less than
perfect, because the central maintainer of BASIC-256 is a
working stiff with a lot of higher priorities and not very
many knowledgeable geeks helping him out.

One place where I did see a recent version of BASIC-256
was in the FreeBSD world. In the hope of making things
easier, I installed PCBSD....

http://www.pcbsd.org/

....but I then discovered that I couldn't get Internet access
at all, and I wasn't inclined to fight through all the possible
causes when I knew I had Linux distros that handled the
web just fine on the same laptop.

The important thing to me is not which distro I run; I've
tried enough of them to know that they all have their various
strengths and weaknesses. What I want is an environment
which gives me an acceptable GUI (I can live with either
Gnome or KDE, and I won't rule out some of the other
choices), a few common apps (a decent browser, LibreOffice,
Abiword, Gimp, some others), and the ability to upgrade the
more obscure apps I use (like BASIC-256) in a way that
is *reliable* (that's the top priority) and doesn't force me to
struggle through some new weird sort of minefield each
time I do an upgrade. If possible, I'd like to have a short
script I can run every time an upgrade is required, with
few (if any) changes to the script each time.

LM mentioned the more geekish distros like Slackware
and Gentoo. Even if they are a bit harder to install up
front, I might be willing to go through the process if the
payoff is an environment with greater reliability and
control down the road.

There's an idea that I want to toss in, since this group is
aimed at education.... It might be useful to make my
situation the basis for a school's class project, presumably
at the level of high school or college undergrad. As the
students worked on ways to give me what I need, they
(and I) would learn more about the details of Linux;
they would also get experience in providing technical
support to an end user. I figure it couldn't hurt.

Anyway, you now have some of the background. I'll
check out the resources that Daniel mentioned. I look
forward to seeing your further comments.

Joel
###
To unsubscribe from the schoolforge-discuss mailing list:
Send an e-mail message to majordomo@xxxxxxxxxxxxxxx with no subject
and a body of "unsubscribe schoolforge-discuss"


###
To unsubscribe from the schoolforge-discuss mailing list:
Send an e-mail message to majordomo@xxxxxxxxxxxxxxx with no subject
and a body of "unsubscribe schoolforge-discuss"


###
To unsubscribe from the schoolforge-discuss mailing list:
Send an e-mail message to majordomo@xxxxxxxxxxxxxxx with no subject
and a body of "unsubscribe schoolforge-discuss"