newforrestgump001 / imageclipper

Automatically exported from code.google.com/p/imageclipper
0 stars 0 forks source link

Patch for Makefile to compile on gcc4.5 and dirty hack for __BEGIN__ __END___ macros aswell as gcc4.5 header compatibility #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Index: imageclipper.cpp
===================================================================
--- imageclipper.cpp    (Revision 102)
+++ imageclipper.cpp    (Arbeitskopie)
@@ -21,6 +21,12 @@
  * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
  * THE SOFTWARE.
  */
+
+/* DIRTY FIX DIRTY FIX */
+#define __BEGIN__ {
+#define __END__ goto exit; exit: ; }
+/* DIRTY FIX DIRTY FIX */
+
 #ifdef _MSC_VER // MS Visual Studio
 #pragma warning(disable:4996)
 #pragma warning(disable:4244) // possible loss of data
Index: icformat.h
===================================================================
--- icformat.h  (Revision 102)
+++ icformat.h  (Arbeitskopie)
@@ -30,6 +30,7 @@

 #include <stdio.h>
 #include <string>
+#include <cstdio>

 /**
 * Convert format to string
Index: Makefile
===================================================================
--- Makefile    (Revision 102)
+++ Makefile    (Arbeitskopie)
@@ -9,7 +9,7 @@
 LINK = g++
 INSTALL = install
 CFLAGS = `pkg-config --cflags opencv` -I ~/usr/include/boost-1_36 -I.
-LFLAGS = `pkg-config --libs opencv` -L ~/usr/lib -lboost_system-gcc41-mt 
-lboost_filesystem-gcc41-mt
+LFLAGS = `pkg-config --libs opencv` -L ~/usr/lib -lboost_system-mt 
-lboost_filesystem-mt
 all: imageclipper

 imageclipper.o: imageclipper.cpp

Original issue reported on code.google.com by timo.witte on 26 Dec 2010 at 2:10

GoogleCodeExporter commented 9 years ago
Same issue, though timmo.witte's diff is smaller. A move to autoconf or cmake 
would be great.

Original comment by lmwa...@gmail.com on 7 Mar 2011 at 7:24

Attachments:

GoogleCodeExporter commented 9 years ago
lmwangi´s patch is a lot better! I just did mine for a fast fix to just 
compile the app. autoconf / make would be great.
I think the owner of this project just did this tool for himself and published 
it like that. If you do a small tool for a simple job you wouldn´t use 
autoconf / make either i think.

Original comment by timo.witte on 7 Mar 2011 at 9:10