NetBeans - Revision history

Tino Didriksen: /* Apertium */

2017-06-03T10:21:15Z

Apertium

Tino Didriksen at 15:19, 2 June 2017

2017-06-02T15:19:41Z

Tino Didriksen: work-in-progress

2017-06-02T15:05:14Z

work-in-progress

Tino Didriksen: work-in-progress

2017-06-02T14:48:31Z

work-in-progress

Tino Didriksen: work-in-progress

2017-06-02T14:29:19Z

work-in-progress

New page

If you want to work with the Apertium native core tools, but you really don't want to go through the arduous process of command line debugging, you can instead use a combination of [[Install Apertium core by compiling|initial command line setup]] and then have [https://netbeans.org/ NetBeans] take over.

== NetBeans ==
First thing you need is to install NetBeans from somewhere. If on Debian/Ubuntu, <code>sudo apt-get install netbeans</code> will do. Once installed, you probably need to add the <code>C/C++</code> plugin.

From Tools → Plugins:
* In the Settings tab, enable all Update Centers.
* Then in Available Plugins, hit "Check for Newest" and find the <code>C/C++</code> plugin.
* Then in Updates, hit "Check for Updates" and update all available plugins.

== Lttoolbox ==
Initial command line setup:
<pre>
svn co https://svn.code.sf.net/p/apertium/svn/trunk/lttoolbox
cd lttoolbox
autoreconf -fi
./configure --enable-debug
</pre>

Then from NetBeans, File → New Project → C/C++ → C/C++ Project with Existing Sources

== Apertium ==
Assuming you did all this in /home/tino/Desktop, you'd do <code>export 'APERTIUM_CFLAGS=-I/home/tino/Desktop/lttoolbox/ -I/usr/include/libxml2/ -L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/' 'APERTIUM_LIBS=-L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/ -llttoolbox3'</code>

@@ Line 48: / Line 48: @@
 Proceed similarly to lttoolbox by creating the project with existing sources, and selecting the binary to debug.
+[[File:Apertium-20-make.png|200px|none]]
 Then from Run, adjust the Environment by adding LD_LIBRARY_PATH pointing to both the lttoolbox and apertium .libs folder that has the built libraries, and setting LC_ALL to a UTF-8 capable locale:

@@ Line 37: / Line 37: @@
 == Apertium ==
+Initial command line setup. Since we do not <code>make install</code> anything, we need to define the <code>APERTIUM_*</code> envvars manually:
-<code>export 'APERTIUM_CFLAGS=-I/home/tino/Desktop/lttoolbox/ -I/usr/include/libxml2/ -L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/' 'APERTIUM_LIBS=-L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/ -llttoolbox3'</code>
+<pre>
+svn co https://svn.code.sf.net/p/apertium/svn/trunk/apertium
+cd apertium
+autoreconf -fi
+export 'APERTIUM_CFLAGS=-I/home/tino/Desktop/lttoolbox/ -I/usr/include/libxml2/'
+export 'APERTIUM_LIBS=-L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/ -llttoolbox3'
+./configure --enable-debug
+</pre>
+Proceed similarly to lttoolbox by creating the project with existing sources, and selecting the binary to debug.
+Then from Run, adjust the Environment by adding LD_LIBRARY_PATH pointing to both the lttoolbox and apertium .libs folder that has the built libraries, and setting LC_ALL to a UTF-8 capable locale:
+[[File:Apertium-40-env.png|200px|none]]
+Also adjust the Run Command to what you actually want to debug:
+[[File:Apertium-30-run.png|200px|none]]

@@ Line 1: / Line 1: @@
 If you want to work with the Apertium native core tools, but you really don't want to go through the arduous process of command line debugging, you can instead use a combination of [[Install Apertium core by compiling|initial command line setup]] and then have [https://netbeans.org/ NetBeans] take over.
+Paths are going to reference <code>/home/tino/Desktop</code> as that is where I tested this. Substitute with your own paths.
 == NetBeans ==
@@ Line 23: / Line 25: @@
 Next, Browse to the folder that has the project's configure.ac file. Leave everything else as-is and Finish:
 [[File:Netbeans-30-new.png|200px|none]]
+From Project Properties, in the Build → Make foldout, adjust the Build Command with more -j if you want, and set the Build Result to the executable you want to debug. Make sure to select the actual binary from .libs and not the wrapper script:
+[[File:Lttoolbox-20-make.png|200px|none]]
+Then from Run, adjust the Environment by adding LD_LIBRARY_PATH pointing to the .libs folder that has the built libraries:
+[[File:Lttoolbox-30-run.png|200px|none]]
+Also adjust the Run Command to pass it the arguments and files you need. In order to echo input directly to the command, instead append to the Run Command as a redirect file like <code><(echo "input goes here")</code>
+And you're good to go. You should now be able to run, debug, set breakpoints, inspect state, and everything else you expect from working with an IDE.
 == Apertium ==
-Assuming you did all this in /home/tino/Desktop, you'd do <code>export 'APERTIUM_CFLAGS=-I/home/tino/Desktop/lttoolbox/ -I/usr/include/libxml2/ -L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/' 'APERTIUM_LIBS=-L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/ -llttoolbox3'</code>
+<code>export 'APERTIUM_CFLAGS=-I/home/tino/Desktop/lttoolbox/ -I/usr/include/libxml2/ -L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/' 'APERTIUM_LIBS=-L/home/tino/Desktop/lttoolbox/lttoolbox/.libs/ -llttoolbox3'</code>

@@ Line 18: / Line 18: @@
 </pre>
-Then from NetBeans, File → New Project → C/C++ → C/C++ Project with Existing Sources
+Then from NetBeans, File → New Project → C/C++ → C/C++ Project with Existing Sources:
+[[File:Netbeans-20-new.png|200px|none]]
+Next, Browse to the folder that has the project's configure.ac file. Leave everything else as-is and Finish:
+[[File:Netbeans-30-new.png|200px|none]]
 == Apertium ==