upp-posix  15947
About: Ultimate++ is a C++ cross-platform rapid application development framework. Stable release.
  Fossies Dox: upp-posix-15947.tar.xz  ("unofficial" and yet experimental doxygen-generated source code documentation)  

upp-posix Documentation

Some Fossies usage hints in advance:

  1. To see the Doxygen generated documentation please click on one of the items in the steelblue colored "quick index" bar above or use the side panel at the left which displays a hierarchical tree-like index structure and is adjustable in width.
  2. If you want to search for something by keyword rather than browse for it you can use the client side search facility (using Javascript and DHTML) that provides live searching, i.e. the search results are presented and adapted as you type in the Search input field at the top right.
  3. Doxygen doesn't incorporate all member files but just a definable subset (basically the main project source code files that are written in a supported language). So to search and browse all member files you may visit the Fossies upp-posix-15947.tar.xz contents page and use the Fossies standard member browsing features (also with source code highlighting and additionally with optional code folding).
U++ POSIX Installation

U++ for POSIX (Linux, OpenBSD, FreeBSD, OpenSolaris) comes as single sandboxed
archive. After downloading, you need to unpack this archive to suitable location with

tar xf upp-posix-14411.tar.xz

(replace 14411 with the revision you have downloaded). Of course, you can use
your desktop environment GUI desktop utility as well.

This will produce "upp" folder full of files.

cd upp

to get into it. Now you have two options:

- Use ./install script that should resolve all dependencies and build theide
  as fast as possible (usually the process takes a couple of minutes). Note that
  this does not work for OpenBSD (see bellow).

- Resolve dependecies yourself and use make to build theide. Even if you do this,
  peeking into ./install is a good idea to get a clue about dependecies
  required. You should also build umk command line too with
  make -f uMakefile, also this is not strictly necessarry for the first
  taste of U++. On non-Linux systems, you should run ./configure first.

At the end of this process, you should have two binaries in the folder, theide
and umk. Start theide to have some fun with U++.

As long as you keep theide (or umk) just in the original directory, nothing
will be written outside of it - its "sandboxed" (with one exception described
bellow). If you get bored with U++ and need to clean the space, simply delete
the "upp" folder.

If you move theide e.g. to ~/bin, it will start to write things to ~/.config
and ~/.cache.

The exception to the sanboxing rule is single command invoked from TheIDE menu,
Setup / Install theide.desktop. This will write proper .desktop file to
~/.local/share/applications - the effect of this on most desktop environments
is that TheIDE will appear in the desktop menu somewhere, usually in the Start
menu under Programming category. Sometimes desktop environment needs restart
for this to take effect.

OpenBSD specific notes

In OpenBSD you need to resolve dependencies manually before running the ./install script by

pkg_add bash pkgconfig

(this should work as long as you have installed desktop environment before installing U++).

It is also necessary to increase the allowed memory sizes in /etc/login.conf to


otherwise compiler will run out of memory.