Install PSIMAP js

From PSIMAP

PSIMAP_js.exe : console application for Microsoft Windows.
PSIMAP_GUI_js.exe: GUI wrapper for PSIMAP_js.exe.
psimap_js : console application for Linux.

PSIMAP_js.exe and PSIMAP_GUI_js.exe are compiled and tested on Microsoft Windows XP Home Edition Service pack 1 and Microsoft Visual C++ 6.0. psimap_js is compiled by GNU g++ 3.4.3 on Linux Fedora Core 3.

Source Distribution

PSIMAP_CUI_MSW.zip : Source for console version of PSIMAP_js on Microsoft Windows.
PSIMAP_GUI_MSW.zip : Source for GUI versioin of PSIMAP_js on Microsoft Windows.
PSIMAP_Linux_Fedora_Core3.zip : Source for Linux version of PSIMAP_js.

2.1. File description

2.1.1. psimap_interface_ljs.cpp

This file contains 'main' function of C/C++. All operations needed in finding interface are performed in this file. It contains many code fragments processed by pre-processor. As a result, this file can be compiled on Linux, Windows by defining MACRO constants. Refer to 2.2.2 for the macro constants.

2.1.2 pdbatom.h, pdbatom.cpp

These files define CPDBAtom object which represent an atom in pdb-style file.

2.2 Compile

2.2.1. Output path in Microsoft Windows

On Microsoft Windows, executibles are created on parent folder of your working directory. You can change this behavior by the follow way with Microsoft VIsual C++ 6.0 :
   Select [Project]-[Settings] from Menu, or press [ALT+F7]. Then Select 'Link' tab and 'General' item in 'Category' combobox. You can see the path and name of an executible at the below of 'Output file name:' You can change output file path and name if you want.

2.2.2 Macro constants

The number of heading and trailing underlines of each macro constant is 2.

2.2.2.1 __COMPILE_ON_LINUX__

: You should define this macro when you compile psimap_interface_js.cpp on Linux like this:
#define __COMPILE_ON_LINUX__

2.2.2.2 __COMPILE_ON_WINDOWS__

: You sould define this macro when you compile psimap_interface_js.cpp on Microsoft Windows:
Launch Microsoft Visual C++ 6.0 and open PSIMAP_cs.dsw or PSIMAP_GUI.dsw and press ALT-key with F7, or select [Project]-[Setting] from Menu. Select [C/C++] tab and set [General] in 'Category' combo box. You can find a text box titled 'Preprocessor definitions:'. Add __COMPILE_ON_WINDOWS__ to the text box. Compile.

2.2.2.3 __WINDOWS_CONSOLE__

: You should define this macro when you compile psimap_interface_js.cpp on Microsoft Windows as a console version. You can define this macro by the same way in 2.2.2.2, but in this case a file name should be PSIMAP_cs.dsw.
N.B: You must define __COMPILE_ON_WINDOWS__ too when you want to compile console version in Microsoft Windows.

2.2.3. Microsoft Windows Console: PSIMPA_CUI_MSW.zip

Open PSIMAP_cs.dsw with Visual C++ 6.0. Define __COMPILE_ON_WINDOWS__ and __WINDOWS_CONSOLE__ according to the way described in 2.2.2.2 and 2.2.2.3. After that, compile. Then you can see 'PSIMAP_js.exe' at the immediate parent folder of your working directory or the path described in 2.2.1.

2.2.4. Microsoft Windows GUI : PSIMAP_GUI_MSW.zip

Open PSIMAP_GUI.dsw with Visual C++ 6.0. Define __COMPILE_ON_WINDOWS__ according to the way described in 2.2.2.2 and 2.2.2.3.

IMPORTANT: You should put the line #include "stdafx.h" at the first of the psimap_interface_ljs.cpp file.
After that, compile. Then you can see 'PSIMAP_GUI_js.exe' at the immediate parent folder of your working directory or the path described in 2.2.1. You should not define __WINDOWS_CONSOLE__ macro.

2.2.5. Linux : PSIMAP_Linux_Fedora_Core3.zip

Open psimap_interface_ljs.cpp. If there is no line defining preprocessor macro __COMPILE_ON_LINUX__, define the macro constant by the way in 2.2.2.1. And then compile with g++:
g++ -o psimap_js pdbatom.o psimap_interface_ljs.cpp

If there is no pdbatom.o file, you should make it before compiling psimap_interface_ljs.cpp:
g++ -c pdbatom.cpp
N.B You should not use gcc when compiling this program even though manual says that gcc calls g++ when it compiles a file of which extension is cpp.