U++ Forum - RDF feed
https://www.ultimatepp.org/forums/
Compiling a POSIX Package
https://www.ultimatepp.org/forums/index.php?t=rview&goto=49125&th=10208#msg_49125
************************************************************ **********************************
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.
Installation
------------
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.
```bash
./configure
make
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:
____________________________________________________________ ______________
LANG = C
LC_ALL = C
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.
Thanks!
]]>morley2017-12-21T06:37:56-00:00Re: Compiling a POSIX Package
https://www.ultimatepp.org/forums/index.php?t=rview&goto=49126&th=10208#msg_49126
I am not familiar with that package, but I am familiar with using 3rd party packages -especially C libararies- in U++ libs and apps.
My strategy would be to first successfully compile the relevant 3rd party package separately on the target platform (using make, or cmake if possible), and then look into the config.h (or whatever config files created by configure/make/cmake. They usually create a final config.h which contains the necessary preprocessor flags that will let the package compile). Then add the source code of the given package to my app, and it's config.h (or whatever it is named) file.
Since this package supports Windows and MinGW, same strategy should apply to the MinGW builds.
This method always worked for me.
Best regards,
Oblivion]]>Oblivion2017-12-21T08:20:56-00:00Re: Compiling a POSIX Package
https://www.ultimatepp.org/forums/index.php?t=rview&goto=49152&th=10208#msg_49152
Best wishes for the new year from Minnesota. Saturday's High and low expected to be -21 and -26C! ]]>morley2017-12-28T05:32:33-00:00Re: Compiling a POSIX Package
https://www.ultimatepp.org/forums/index.php?t=rview&goto=49155&th=10208#msg_49155
]]>koldo2017-12-28T09:00:27-00:00