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
ProGuard on Windows vs. Linux
I can use ProGuard to shrink and obfuscate my exported P2.1 application in Windows 8. It does a good job with excellent results (except ControlP5 controls don't function in obfuscated version - getting close) . On a Linux system (Lubuntu 13.2) when I export my application to a Linux application and do the exact same process with ProGuard the resulting shrunken and obfuscated .JAR does not work, and my application crashes without rendering the screen. ProGuard reports a successful run on it's end, so I don't have an error report to track down.
I expected the same results/outcome on either platform. The Linux application has more library .JAR's to reference, but otherwise shouldn't they be the same?
Anyone know what would cause this Windows vs. Linux difference? In there a workaround of special parameters for Linux I need to address?
Thanks in advance.