Hi, All!

How can i send fasm to insert in obj (format COFF) command for linker to use specific lib? Same as /DEFAULTLIB:libfile command to microsoft link?

Obj format supports it, but do support fasm?

thanks...

no. To use any library in COFF format you have to use some external linker, like GoLink or ALink.

This could be done by making the '.drectve' section in COFF object, but fasm currently doesnt' have any setting that would allow you to set IMAGE_SCN_LNK_INFO flag for such section, which is needed for it to be recognized by linker. If you suggest any good name for such flag setting (something like the already used "executable" or "discardable" flags), it can be implemented quickly.

When I was developing the first COFF-able version of fasm (it was 1.39, if I recall correctly) I was trying it with some temporarily chosen flag name and I was successful - all parameters passed inside the '.drectve' section were used by linker and section was not included in executable.

what about calling it simply 'linkinfo'? or perhaps 'linkparms'?

What about linklib or even inslib or libinsert?

you can use the linker comment for more than just inserting libraries, though - like specifying /FILEALIGN or whatever.

Privalov
If you suggest any good name for such flag setting

virtual

Because this section not include for executable module.
?

Better '.virtual' ?

2 Privalov
If you suggest any good name for such flag setting (something like the already used "executable" or "discardable" flags), it can be implemented quickly.

Please, this feature is very important. Because when you have more than 70 different lib's it's very hard ot write all in command line for link instead write only 'include filex.inc'...

uri is right. Don't forget about DOS command line size limitation.

2 Privalov: and what you think about this thread?

Heh. For all, who want to use options for ms link (like /DEFAULTLIB) from asm code (with format MS COFF):

First: we must patch fasm sources. We must open FORMATS.INC and add to formatter_symbols (at the end of file) table this lines:

Attension: you must preserve alphabetically order in this table !!!

You must get like this:


Ok, now we must go to VERSION.INC and change version number to 1.55b (or other version, if you wish).

And now we must recompile fasm: fasm fasm.asm fasm.exe (or fasmw.asm if you want to use fasmw).

Thats all.

To have new abilities we must write in our asm code lines like this:


and when you will link this file (obj file, what will get from this asm) ms link will add to command line text from .drectve section.

One moment. We add new option hidden. This option say to link do not add section to executable and you can use this sections to add comments (or copyrights) to you obj file, like this:

You will have this text in obj, but do not have in exe (or dll, or ...).

Thank you Privalov. Fasm the best !!!

will this feature become part of fasm someday?

I prefer the "linkinfo" name for the IMAGE_SCN_LNK_INFO flag. Still haven't decided for the IMAGE_SCN_LNK_REMOVE, but "hidden" seems to be a good choice.

The "linkinfo" and "hidden" are added as a "hidden" updated to the 1.64

Seems that you wish to keep version number 1.64 as long as it is possible

The 1.65.x development line is supposed to focus on the different things in my plans and I don't want to start it prematurely.

decard: it's a good version number

Off-topic: Version 1 means it is mature and 64 is the ability to compile a 64-bit binary file.

Only a 64 bit (8 byte) file! What if I need a file bigger than that, say 9 bytes in length? What if I need a file smaller than that, say 7 bytes in length?