This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

GNU Assembler and Link Errors




Hi, I am working on a project that requires me to use the Microsoft Compielr and Linker to build both DLL's and binaries. However, I do have an assembly language file that needs to get built as well.

Because this software already runs on Solaris (SPARC and X86) and Linux, this assembly language file gets assembled using GNU's assembler on Linux/X86. So when the port to Windows stats, I think why not use GNU's assembler on the Linux Assembler file and be done with it.

Well, it not working out like I thought. The process is this:

		1) Using GNU's assembler, create an object file.
		2) Using Microsofts COmpiler, compile all other C
		   sources files.
		3) Use Microsofts linker to create a DLL of the object
		   files produced from (1) and (2).

Well, I can't seem to link the DLL because there are link errors on the functions that reside in the object file created by GNU's assembler.

Is there anything one has to do above and beyond in the assembler file itself when porting form Linux to Windows for the sysbols to recognized using Microsofts linker? The functions are already declared global using the ".globl [func-name]" directive.

Right now I'm thinking my only alternative is to rewrite the file using NASM, or MASM, or some other assembler.

Any help is apprecieated.


Thanks, Jim













--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]