Bloody compilers

[Weltchy]

Yer but I love it

(when it compiles)

me too, me too!

On a sidenote however, can I point out that widgets are in fact used in Java, not .Net. We have controls, not widgets!!

[suityou01]

Code Monkey work

Yer but I love it

(when it compiles)

[Weltchy]

Hactually this is one of many module that comprise my plan B

I have successfully compiled all of my modules without problem.

This one module is being a sod.

DP, you'll notice how I have implemented a work around using my own nous. This is real coding, not just plugging .net widgets together.

HTH

Code Monkey work

[OrangeHopper]

Do you maybe need " marks around the path, because it has a space in it?

And you do need the quotes. Standard DOS requirement.

[suityou01]

Hactually this is one of many module that comprise my plan B

I have successfully compiled all of my modules without problem.

This one module is being a sod.

DP, you'll notice how I have implemented a work around using my own nous. This is real coding, not just plugging .net widgets together.

HTH

[OrangeHopper]

I think you need individual -I's, one for each include path, and I would want the -o in front of the target file name.

[AtW]

I like how you post a "hard C question" and then post this.

Can't even compile my-first-noddy.exe

MY-FIR~1.EXE

[DimPrawn]

I like how you post a "hard C question" and then post this.

Can't even compile my-first-noddy.exe

[AtW]

Get Visual Studio C++ (and Intel C++ on top of it if you are really serious) and you won't have to mess about with command line...

[suityou01]

Do you maybe need " marks around the path, because it has a space in it?

Thanks for the reply. I tried it. And I copied the header files to a location with no spaces and tried that.

I am creating a custom header file for the moment to satisfy my requirements, but that is terrible really.

[ee61re]

Do you maybe need " marks around the path, because it has a space in it?

[suityou01]

FFS

I have a simple exe that I was compiling

gcc -o mylittleapp.exe main.c otherfile.c

Now one of the headers needs to use headers in the SDK

Fair enough

I get a compile error saying WTF is this header file

eg other.c has a header file called other.h

other.h has the line

#include "someSDKheader.h"

So I need to include the path to these headers in my search paths right?

Fraking how????

Lets say the headers live in C:\Windows SDK\include

I would need to adjust my compile command to

gcc -o -IC:/Windows SDK/include mylittleapp.exe main.c otherfile.c

right?

So WTF doesn't it work?

I still get

someSDKheader.h file not found

Why? I have included the search path?