OS/2, eCS & ArcaOS - Technical > Programming

trying a first port

(1/2) > >>

Meeko:
My primary language is Python, so I know I am at a disadvantage here. I picked something to start with I thought would be fairly easy: https://sourceforge.net/p/gnaw/wiki/Home/

I installed emx0.9d and gcc3, then compiled the included sieve.c and hello.cc.

I downloaded gnureadl and started to integrate it into the emx tree. I moved some files into emx\bin, emx\dll, and emx\lib, and the included readline.exe works.

There is no documentation stating which source files are needed to build readline itself and which are needed to compile something that uses readline. From the examples directory I am guessing I need history.h, posixstat.h, and readline.h in emx\include. There may be more to do. In the examples directory I see both
--- Code: ---#include "readline.h"
--- End code ---
and
--- Code: ---#include <readline/readline.h>
--- End code ---
. So do I put header files in emx\include or emx\include\readline?

The examples directory has a Makefile.in. Nice, but I don't have configure or bash to work with. It seems the .c's do not depend on each other in any way, so I think I can do single gcc commands and not need to use make. If I can get working .exe's from these, I think I will be ready to try my real project.

Dave Yeo:
EMX is old and superseded by klibc, http://trac.netlabs.org/libc/wiki, more on that below.
We don't really have a good bash port, I've found the best shell to be pdksh, available on hobbes. Generally configure scripts will run with just setting exeext and even libtool can produce working dlls with minimal patching (does everything right then symlinks the import lib to the dll due to long and short names not matching, OS/2 has a 8.3 limit on dlls)
Currently most people are using yum/rpm to install a build environment as well as other software. Most software is close to up to date, eg GCC 4.9.2, Python 2.7.6. See http://trac.netlabs.org/rpm/wiki

Mentore:

--- Quote from: Dave Yeo on February 16, 2015, 07:50:47 am ---EMX is old and superseded by klibc, http://trac.netlabs.org/libc/wiki, more on that below.
We don't really have a good bash port, I've found the best shell to be pdksh, available on hobbes. Generally configure scripts will run with just setting exeext and even libtool can produce working dlls with minimal patching (does everything right then symlinks the import lib to the dll due to long and short names not matching, OS/2 has a 8.3 limit on dlls)
Currently most people are using yum/rpm to install a build environment as well as other software. Most software is close to up to date, eg GCC 4.9.2, Python 2.7.6. See http://trac.netlabs.org/rpm/wiki

--- End quote ---

Hello Dave, could you please explain better "setting exeext"? I didn't know about that.

(Actually I'm not getting more than command line programs. Seems my SDL and Qt configuration is broken, so that Cmake and configure scripts cannot continue. Will solve it asap.)

Meeko:
I got ftp://ftp.netlabs.org/pub/gcc/GCC-3.3.5-csd6.zip and it looks like I can unzip it onto my \emx tree, but nothing says this is (not) the right thing to do. Does it need any environment variables or any other setup beyond what emx 0.9 did?

Dave Yeo:
Easiest is to have a config.site file. The config.site file will be automatically found if at $PREFIX/share/config.site or found by set CONFIG_SITE.
Also note that different shells work different and with the RPM/YUM environment and ash as the shell you're better off recreating the auto files.

--- Code: ---export ac_executable_extensions=.exe
export ac_exeext=.exe

--- End code ---
You can add other needed stuff if configure has a problem finding it

--- Code: ---export INSTALL=f:/usr/bin/install.exe
export lt_cv_path_SED=sed.exe
export lt_ac_sed=sed.exe

--- End code ---

Navigation

[0] Message Index

[#] Next page

Go to full version