Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To configure Eclipse for building and debugging FIX Antenna's samples or your own applications based on FIX Antenna library you can follow these steps:

 

1.       We presume our workspace here:

...

  1. Assumptions:
    • The workspace is located under the following path:

Image Added

 

...

    • FIX Antenna distribution is located in a directory above: /home/mute/sample/

...

    • Xerces-c

...

    • library is installed

...

    • on the machine.

 

 

2.       Add empty C++ project for each sample executable (for example for “Listener”):

...

 

Image Added

 

 Click “Next”.                                                                 

 

3.       Such The following window should will appear:

...

 

Image Added

Click “Finish”.

...

4.       You should be able to see the project in projects explorer:

Image Removed

 

          

5.       Repeat steps 2-4 for “Sender” to make both projects appeared in projects explorer:

...

Image Added

 

 

6.       Add projects dependencies: Path to FixAntenna headers :- for all projects

 

                

 

7.       Then add Add paths to libraries (both FixAntenna & xerces-c) - for all projects:

 

 

 

8.       Be sure to make 6-7 both  for “Listener” & “Sender”, then add Add reference to FixAntenna library in linker settings tab sheet (also do it for both projects)- for all projects:

 

 

9.       Add build targets for both projects (do the same for “Sender” as for “Listener”)all projects:

 

 

 

10.   Build targets:

 

Eclipse should not indicate any errors on this step. If else – please, re-check projects paths/libraries/linker settings.

 

                 

11.   Now, create Create launch configurations for debug (repeat the same for “Sender”)- for all projects:

 

Specify LD_LIBRARY_PATH under the “Environment” tab-sheet named “Environment” likewise :

 

                 

12.   Apply changes and click “Debug”. Eclipse should switch into “Debug” perspective and show debugger tracing:

...