Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.platform
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Compiling XPCOM with gecko-sdk 15 and above.
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
dblino...@gmail.com  
View profile  
 More options Nov 5 2012, 6:20 am
Newsgroups: mozilla.dev.platform
From: dblino...@gmail.com
Date: Mon, 5 Nov 2012 03:20:05 -0800 (PST)
Local: Mon, Nov 5 2012 6:20 am
Subject: Compiling XPCOM with gecko-sdk 15 and above.
Print | Individual message | Show original | Report this message | Find messages by this author
Hello.

I have binary c++ XPCOM component. I've tried to build it with xulrunner-sdk-15.0.1 (16 and above) and receive linker error:

xpcomglue_s.lib(nsStringAPI.obj) : error LNK2001: unresolved external symbol __imp___snprintf
xpcomglue_s.lib(nsCRTGlue.obj) : error LNK2001: unresolved external symbol __imp__rand
xpcomglue_s.lib(nsCRTGlue.obj) : error LNK2001: unresolved external symbol __imp__srand
xpcomglue_s.lib(nsCRTGlue.obj) : error LNK2001: unresolved external symbol __imp___fdopen
xpcomglue_s.lib(nsCRTGlue.obj) : error LNK2001: unresolved external symbol __imp___dup

But I compiled it with previous xulrunner versions without errors.
Looks like they changed "Use Run-Time Library" compiler option from /MT (Multi-threaded) to /MD (Multi-threaded DLL). As I understand, the problem can be solved changing "Use Run-Time Library" in my project from /MT to /MD.
Unfortunately we are using /MT compiler option in our solution and can’t change them. I recompiled gecko sdk from sources and obtained the same result. But I can’t find out how do I change compiler options to build gecko libraries with needed runtime library usage.
Could anybody give me a hint where in the sdk these options could be changed?


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
jim.math...@gmail.com  
View profile  
 More options Nov 6 2012, 4:15 pm
Newsgroups: mozilla.dev.platform
From: jim.math...@gmail.com
Date: Tue, 6 Nov 2012 13:15:44 -0800 (PST)
Local: Tues, Nov 6 2012 4:15 pm
Subject: Re: Compiling XPCOM with gecko-sdk 15 and above.
Print | Individual message | Show original | Report this message | Find messages by this author
You should look at the new glue libraries that statically link to the crt on Windows -

XPCOM_STANDALONE_STATICRUNTIME_GLUE_LDOPTS
XPCOM_STATICRUNTIME_GLUE_LDOPTS

I believe components use the standalone which is what we use for our exe stubs.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google