Polink/Polib bugs

[akyprian]

Hi,

I 'd like to use Polink and Polib from within WinAsm Studio. It seems that I got errors when using the /OUT: switch.

More specifically, I use a response file and enclose the output file name in quotes. Polink/Polib do not like quotes for the out file name. They do not like file names that contain spaces either.

A quick fix for this problem would be appreciated.

Regards,

Antonis

PS.I 'd like /LIBPATH to be supported by Polib too

[GregL]

akyprian,

I ran into the same problem with Polink. Here is a link to a post on the Pelle's C Forum with the solution.

http://smorgasbordet.com/phpBB2/viewtopic.php?t=691

[akyprian]

Thanks for the solution Greg, although I 'd be glad to see the command line handled properly. I am sure the WinAsm Studio users will complain a lot about this.

Regards,

Antonis

[akyprian]

In any case, I am using a response file, in which case I don't understand how the argv array is invlolved.

Thanks again,

Antonis

[rags]

I am using a response file

please exuse my ignorance, but what is a response file?
regards,
rags

[PellesC]

In any case, I am using a response file, in which case I don't understand how the argv array is invlolved.

Same basic algorithm: if a new token starts with a single or double quote, it is seen as a single token - otherwise normal white space is used.

This is by design, and I see very little reason to change it...

Pelle

[akyprian]

Hi,

If it is not compatible with common practice, this is a very good reason to change it. Polink's and Polib's command line arguments are very similar to those of ms link and lib, which means you wanted to follow some widely used practice. If every linker/library manager (or any other application) handles arguments in any way the developer decides to adopt, that would make life harder for the rest.

I wish, You will make second thoughts

Antonis

[hutch--]

rags,

A response file is an old trick from the days of DOS with command line limits but it is very useful when you have a large number of modules to include on a link command line. Instead of typing them one after another on the command line, you make a response file where the first module is the one for the application and any other required modules are added after it.

The response file is just a list of object moduls and the normal convention for using them with a linker is to just put the response file with an "@" symbol in front of it so you use "@myapp.rsp" to place all of the object modules on the command line.