makefile and windows compilation

Hi guys,
Im not a C expert or anything and I need help with this issue. I have a long code (10 files or so), that I didn't write. It has a makefile, and all I have to do is type "make" in unix and it complies without errors or warnings, and it work.

I've been trying to compile this in windows, using visual studio, but it gives me A LOT of errors. What I do basically is go to the file that contains main, and try to compile it. I can't seem to find what the reason is. I feel like its having a hard time linking the files together. Any ideas or suggestions. I would really appreciate it.

I believe there's a utility called nmake that can compile makefiles.
Compiling the source otherwise is possible, but we cannot say what's wrong without error messages (and parts of the source).

Quote:

---

Originally Posted by Elysia

I believe there's a utility called nmake that can compile makefiles.
Compiling the source otherwise is possible, but we cannot say what's wrong without error messages (and parts of the source).

---

Thanks for your reply. Would nmake compile using visual studio ? Keep in mind this compiles without ANY problems under unix or cygwin using gcc.

I'm not 100% sure how nmake works, but it should be able to compile a makefile.
VS is a little childish to some code - ie won't accept it.
I cannot help correct any compile errors without seeing the code that's responsible for the error, however.

Could it be compiling C code as C++?

No, it's compiled as C alright.

Quote:

---

Originally Posted by Elysia

I'm not 100% sure how nmake works, but it should be able to compile a makefile.
VS is a little childish to some code - ie won't accept it.
I cannot help correct any compile errors without seeing the code that's responsible for the error, however.

---

The code is 14 files and really long. Its very complex, I don't think it would be feasible to post it here or parts of it. I would really like to see what this code is doing under VS debug mode, this is the reason why I would like to be able to compile it in VS.

The other problem is that this when the code is run under Unix environment, it functions properly. However, when I compile it with cygwin (without errors) and run it, one part of it gives me wrong outputs. Again, this is why I would like to the be able to run it under VS debug mode.

You can post the lines that give compile errors, though, not the entire files.

On top of the header files it has:

#ifdef __cplusplus
extern "C" {
#endif /* __cplusplus */


Do you have to tell VS to compile it as C or does it recognize it ?

If the file has a .c extension, it's compiled as C.

Some lines that give error:
line 20:
inline double dist(double, double, double,double,double,double);

Add

Code:

---

#ifdef _MSC_VER
#define inline __inline
#endif

---

To the top of the header.
Visual Studio doesn't like "inline" in C, but __inline works fine.

Quote:

---

Originally Posted by Elysia

Add

Code:

---

#ifdef _MSC_VER
#define inline __inline
#endif

---

To the top of the header.
Visual Studio doesn't like "inline" in C, but __inline works fine.

---

Add that to the top of all headers or just the main header ?

Wherever you see the "inline" keyword.
If you can add it in a main header that gets included in every header, that's even better.
Do what your current code allows you to.

Wow, I added that to the top of the main header, and all the errors are gone, just 26 warning, mostly about unreferenced local variable.
can the warning be due to the fact that Process() is talking to a file called process (lower case p) ?

Most likely, yes. The warning says that there's no prototype for function Process, so the compiler guesses what it looks like, which is bad.
You can also comment out all the unreferenced variables, because VS is telling you they are never used anywhere.

I found out the function definition of Process(), was not included in the main.c or main.h, so I added it to main.h. The warning went away and it compiles without error or warning (just the the "unreferenced local variable", which i will handle later.

Again, this compiles and links perfectly in Unix or cygwin. What could the problem be ?

Did you merely add a...
something Process();
...to the header file?
Without actually implementing such a function?

Quote:

---

Originally Posted by Elysia

Did you merely add a...
something Process();
...to the header file?
Without actually implementing such a function?

---

lol, no, "process.c" is a file which contains the function "Process()" and a bunch of other functions. The function declaration of Process() wasn't included in mc_main.h, so I included it there (and the bunch of other functions there).

But its giving me a linking problems. Process.h doesn't exist, so I'm wondering if I need to create that. But again, it works without problems in unix.

Well, then.
Two other possibilities:

1) Did you copy the exact definition of Process? It must match the header of the function exactly.
2) You aren't compiling the process.c file. Is it excluded? Right-click it and select properties.

Quote:

---

Originally Posted by Elysia

Well, then.
Two other possibilities:

1) Did you copy the exact definition of Process? It must match the header of the function exactly.
2) You aren't compiling the process.c file. Is it excluded? Right-click it and select properties.

---

The definitions match the function headers exactly. I think you are right with #2, i changed the name of process.c to something else, to see if I would still get the same errors and I do indeed. What must be the reason why its not reading it ? Do I need to create header file for it and include it in main.c? Main calls functions from process.c

You said you were in VS. Therefore, you have a solution, which has a project. That project should have "source files" (or something similar). Both of the .c files need to be listed there.

Quote:

---

Originally Posted by tabstop

You said you were in VS. Therefore, you have a solution, which has a project. That project should have "source files" (or something similar). Both of the .c files need to be listed there.

---

Well all I did is compile main.c, and it created a project for me ? Is that wrong? Can I add process.c to the project? Shouldn't it find project.c by itself?

Quote:

---

Originally Posted by inkare

Well all I did is compile main.c, and it created a project for me ? Is that wrong? Can I add process.c to the project? Shouldn't it find project.c by itself?

---

And how would it do that? Search your hard drive for any and every file with a .c extension in the hope that it has the functions you need? Add project.c to your project.

Thanks a lot for your help guys. I've been since using Matlab for a while now, and the entire compilations and linking stuff doesn't make sense to me anymore. I went into project and added all the files necessary to the project. It works, except one last part in linking. This is the error I get.

--------------------Configuration: mc_main - Win32 Debug--------------------
Linking...
main.obj : error LNK2001: unresolved external symbol _dist
Debug/main.exe : fatal error LNK1120: 1 unresolved externals
Error executing link.exe.

main.exe - 2 error(s), 0 warning(s)


Now, dist is an inline function included in another file (utilities.c), which doesn't have a header file. Does the linker look for it, or am I supposed to somehow tell it its there?

Code:

---

inline double dist(double x1, double y1, double z1,
            double x2, double y2, double z2)
{
  double d;
  d=sqrt(DSQR(x1-x2)+DSQR(y1-y2)+DSQR(z1-z2));
  return(d);
}

---

If you need utilities.c, add it to the project.

Quote:

---

Originally Posted by tabstop

If you need utilities.c, add it to the project.

---

I did !!

I copied the function dist in the bottom of main and it compiles and works. :) I don't know why it wasn't able to find it despite utilities.c being added to the project.

I'm trying to run this code in debug mode, but the code takes a file as input. When it gets to the part with the input file (below), debug mode crashes, because i'm not able to provide it with the file. But when I run it from the command prompt, it's able to read the input file. Anyone knows the trick behind it?

Code:

---

int main(int argc, char *argv[])
{   

  input_file_ptr = fopen(argv[1], "r");

....
}

---

If you right click on the project, and select properties, you should see "Debugging" under Configuration Properties. One of the slots on this page is Command Arguments, which should be the things passed to your program in argv.

Quote:

---

Originally Posted by tabstop

If you right click on the project, and select properties, you should see "Debugging" under Configuration Properties. One of the slots on this page is Command Arguments, which should be the things passed to your program in argv.

---

You mean right click the DSP file or the project tab in VS ?

Are you using VS6?

Quote:

---

Originally Posted by Elysia

Are you using VS6?

---

Yes.

Better upgrade, if you can.
VS6 is too different from VS.NET+, plus is not very standards compliant.
(I cannot say what config you mus change & whatnot, because it's too different from VS2008.)

Hi guys ... I've been trying to compile this code for a 64bit machine. It comes with its own Makefile. I don't know how to change the parameters in the makefile to address this change. When I currently compile it under the 64bit machine, in the task manager, It says its a 32bit program. Can someone help me figure it out. Here is the make file:

PS... I'm compiling this code with cygwin in a 64bit windows machine.



CC = gcc
CFLAGS = -O3 -funroll-loops
#CFLAGS= -g

MONTE_LIBS= -lm

MC_OBJECTS= main.o save.o utilities.o nt.o process.o

COMMON = Makefile

all: main3d

main3d: $(MC_OBJECTS) $(COMMON)
$(CC) $(CFLAGS) -o main3d $(MC_OBJECTS) $(MONTE_LIBS)


.c.o:
$(CC) -c $(CFLAGS) $<

clean:
rm -f $(MC_OBJECTS) core
veryclean:
rm -f $(MC_OBJECTS) core main3d *.c~ *.h~