dev-cpp-users Mailing List for Dev-C++ (Page 3)

Note that a number of functions used by MinGW (the compiler with Dev-C++)
is using windows libraries, instead of unix-compatible libraries.

For example, serial ports and networking are win32-based. I noticed
that you had problems with the include file <netinet/in.h>. For
networking, you have to modify the code to use winsock.

When skipping expected include files, things have a tendancy to go down
the drain quite quickly. However, since we are talking about a conversion
program, I would assume that it really don't need any networking support.
Probably just some helper functions or macros from the file. For example
the ntohl/ntohs/htonl/htons functions (or macros depending on
implementation) from converting between host and network byte order in
case any of the raw file formats - or output file formats - happen to use
network byte order of the data.

the glib include gtypes.h does have g_ntohx and g_htonx functions/macros.
Try to scan your include directories for alternative header files that
contains similar or same defines as the ones your compiler is complaining
about.

There is a built-in debugger in Dev-C++, but I can't really recommend it.
I normally use an external debugger. One example is Gnu Visual Debugger
(gvd).

/Per W

On Tue, 3 Oct 2006, IraqiGeek wrote:

> On Tuesday, October 03, 2006 4:21 PM GMT,
> Matt VanAvery <mat...@ya...> wrote:
>
> > I compiled dcraw.c in FreeBSD 6.1 with no problems using:
> >
> > gcc -o dcraw -O4 dcraw.c -lm -DNO_JPEG -DNO_LCMS
> >
> > Matt
> >
>
> Matt,
>
> Thanks for your reply, however my problem is that I'm trying to compile it
> under Dev-C++ 4.9.9.2 without success. So far, I have managed to compile it
> under djgpp without problems using -DNO_JPEG and -DNO_LCMS (note that it
> should compile fine even without those directives, but I dont need those two
> features anyway). The application was written to compile natively on *nix
> systems, which means you shouldn't have any problems compiling it.
>
> I need to trace the execution of dcraw to get to know how its decoding the
> various types of raw image formats. I tried to do that using rhide, but it
> keeps skipping code. I'm used to graphical debuggers (I've been using
> Borland C++ builder for quite some time, and before that used Borland's
> Turbo C++). So, using GDB without any front end (under windows) will be
> quite problematic for me.
>
>
>
> Regards,
> IraqiGeek
> www.iraqigeek.com
>
> What you do speaks so loudly that I cannot hear what you say.
> Ralph Waldo Emerson
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>

On Tuesday, October 03, 2006 4:21 PM GMT,
Matt VanAvery <mat...@ya...> wrote:

> I compiled dcraw.c in FreeBSD 6.1 with no problems using:
>
> gcc -o dcraw -O4 dcraw.c -lm -DNO_JPEG -DNO_LCMS
>
> Matt
>

Matt,

Thanks for your reply, however my problem is that I'm trying to compile it 
under Dev-C++ 4.9.9.2 without success. So far, I have managed to compile it 
under djgpp without problems using -DNO_JPEG and -DNO_LCMS (note that it 
should compile fine even without those directives, but I dont need those two 
features anyway). The application was written to compile natively on *nix 
systems, which means you shouldn't have any problems compiling it.

I need to trace the execution of dcraw to get to know how its decoding the 
various types of raw image formats. I tried to do that using rhide, but it 
keeps skipping code. I'm used to graphical debuggers (I've been using 
Borland C++ builder for quite some time, and before that used Borland's 
Turbo C++). So, using GDB without any front end (under windows) will be 
quite problematic for me.



Regards,
IraqiGeek
www.iraqigeek.com

What you do speaks so loudly that I cannot hear what you say.
Ralph Waldo Emerson 

I compiled dcraw.c in FreeBSD 6.1 with no problems using:

gcc -o dcraw -O4 dcraw.c -lm -DNO_JPEG -DNO_LCMS


Matt

 		
---------------------------------
Stay in the know. Pulse on the new Yahoo.com.  Check it out. 

Hi all,

I'm trying to compile David Coffin's infamous dcraw.c (a raw camera 
converter that supports most cameras out there) mostly so I could trace his 
code to see how he's reading the various raw file formats. However, I can't 
seem to be able to convince dev-cpp 4.9.9.2 to do that.

I am passing -DNO_JPEG and -DNO_LCMS to the compiler, which got me to build 
dcraw.c on djgpp (with rhide).

When compiling on dev-cpp with the above parameters, initially it objects on 
a #include<netinet/in.h>, and after I comment that, it objects saying its 
detecting recursion while expanding a macro within dcraw.c, namely sget4. It 
also says that its detecting recursion on expanding macro image, but as far 
as I can tell, image is a global vector variable.

So, if dev-cpp and djgpp are both based on gcc, why is dcraw.c compiling 
under one and refusing to compile under the other?

dcraw.c can be downloaded from David Coffin's page at: 
http://cybercom.net/~dcoffin/dcraw/

Any help would be greatly appretiated.


Regards,
IraqiGeek
www.iraqigeek.com