Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- cidelab December 2015
- quark December 2015
- subject117 December 2015
Debugging and testing libraries
Hi, Maybe it is silly question. How are you debugging your libraries? Did you create a new Java project and from there import your library? And if is true, exactly how you do it? Could you give me some clues? Kind regards, Thanks in advance Carlosdelab
Comments
In Eclipse, I have one project for the library and another project for Processing sketches. I test the library using sketches I make in the Processing sketches project.
The test project imports libraries so the sketches can run. It needs to import the Processing core.jar file. It also needs to import the library jar file, and maybe other Processing libraries.
When I build my library, the output is put in the Processing's library directory inside the sketchbook location. In my Eclipse workspace, I have a project that is actually a soft link to Processing's library directory. I can easily add jar files to the test project from this library project.
With this setup, when I build the library I must also refresh the library project because Eclipse won't automatically know that the jar file changed. That's a bit inconvenient, but this way I have all the Processing jars in one place and can easily switch between working in Eclipse and working in the Processing IDE without version problems.
There are other ways to do what you want to do, some simpler, but this is how I do it.
Bottom line, you do need to import the library jar file somehow, and you should have a second project for making test sketches.
I have a similar setup to @subject117 in Eclipse. Two projects, the library project and my testing project. Both projects have any Processing jars it needs on the build path e.g. core.jar
There is one big difference. I do not add the library.jar file to the testing project build path. Instead I add the library project itself. It means that I can test the library without having to build the library.jar file every time I make library code changes. This will save you lots of time and effort.
thanks guys, I like both strategies. very useful kind regards.