Status & Roadmap
Authors & License
Funding Ultimate++
Search on this site
Search in forums

SourceForge.net Logo
Home » U++ TheIDE » U++ TheIDE: Compiling, Linking, Debugging of your packages » Compiling a POSIX Package
Compiling a POSIX Package [message #49125] Thu, 21 December 2017 07:37 Go to previous message
morley is currently offline  morley
Messages: 10
Registered: January 2007
Promising Member
Hi Everyone, I am trying to develop some code around this API, which interfaces to the Interactive Brokers trading platform. I would like to learn about automated trading. The gentlemen that developed it made some modifications to the the Interoffice Brokers API to make it run under Posix. I would like to be able to utilize this code. Here is what he writes: I don't want to just compile it though, I want to use upp to do some further work on it. Here is the overview:

************************************************************ **********************************
Portable C++ API for Interactive Brokers TWS

This twsapi is almost identical to the original IB C++ Posix API. It contains
several bugfixes, usage improvements and it's using the autotools build system.
For more details read "Changes of original IB API" below.

The project homepage (bugtracker, latest git repo) is hosted on [github]
Released source tarballs download [here]
Binary rpms for various Linux distros [here]
( http://software.opensuse.org/download.html?project=home:rudi _m&package=twsapi)

Building from source requires a C++ compiler. It has been very well tested with
GNU gcc/g++ and Intel icc/icpc on various Linux distros, MacOSX and
Windows/Cygwin. Native Windows/Mingw is also supported.

When building from git checkout you need both autotools and libtool. Also,
don't forget to type `autoreconf -vfi` first.

make install
************************************************************ **********************************

I would like to be able to compile and to further work on Upp. There are two folders
involved: PosixSocketClient and TestPosixSocketClient.

So my approach was to first build PosixSocketClient as a package, and then reference the package in TestPosixSocketClient. I am having a problem getting PosixSocketClient to build. I think some of the problems are alluded to in the make file:
____________________________________________________________ ______________


SUBDIRS = PosixSocketClient TestPosixSocketClient

nodist_header_HEADERS =
nodist_header_HEADERS += twsapi_config.h

twsapi_config.h: config.h API_VersionNum.txt gen_twsapi_config_h \
$(srcdir)/gen_twsapi_config_h config.h $(srcdir)/API_VersionNum.txt \
$(srcdir)/Shared/EClientSocketBaseImpl.h > $@.tmp \
&& mv $@.tmp $@
____________________________________________________________ ________________

I was able to get through most of the errors which was mostly just pointing upp to the shared header files, however I have some tougher problems with gen_twsapi_config_h. The autorreconf /make file scripts apparently takes gen_twsapi_config.h and turns it into config.h. But there is a lot going on. Can I do this on windows easily, or do I have to do this in linux with autoreconf and make? I am using the mingw64 version of upp.

Read Message
Read Message
Read Message
Read Message
Previous Topic: TheIDE is always stripping debug info in Release configuration with GCC
Next Topic: _Gstaticassertcompiletimeassertion_0 is negative-error
Goto Forum:

Current Time: Thu Jul 09 00:30:07 CEST 2020

Total time taken to generate the page: 0.00963 seconds