#19 <cc outfile=""> is there a way to force the name?

open
nobody
None
5
2005-04-30
2005-04-30
No

Hello,

I am using <cc> and the gcc compiler on windows to
compile and link a .dll. <cc> insists on calling the
outfile lib<mydllname>.so.

I was hoping to control the name with using the
"outfile" attribute. The doc says:

"Sets the output file name. If not specified, the task
will only compile files and not attempt to link. If an
extension is not specified, the task may use a system
appropriate extension and prefix, for example,
outfile="example" may result in "libexample.so" being
created."

It seems that is does add "lib" and ".so" no matter
what I provide with the "outfile" parameter. Is there
a way to do away with the "lib" prefix, and force a
".dll" file extension?

Thanks.
Patrick

Discussion

  • Alan Burlison

    Alan Burlison - 2005-06-19

    Logged In: YES
    user_id=1294929

    I have *exactly* the same problem. I thought cpptasks was
    supposed to be platform-aware, so surely
    outtype="shared"
    should result in foo.dll on winfows, not libfoo.so? Did you
    find a workaround for this?

     
  • Alan Burlison

    Alan Burlison - 2005-06-19

    Logged In: YES
    user_id=1294929

    I hacked round the problem with:
    <linker name="gcc">
    <linkerarg value="-o foo.dll"/>
    </linker>
    but this looks like a bug, so I've raised one - 1223693

     

Log in to post a comment.