it occured clang error
duplicate symbol _CRYPTO_num_locks in:
/proj.ios/frameworks/gpg.framework/gpg(libgpg.a-i386-master.o)
/libs/openssl/lib/libcrypto.a(cryptlib.o)
duplicate symbol _CRYPTO_set_dynlock_create_callback in:
/proj.ios/frameworks/gpg.framework/gpg(libgpg.a-i386-master.o)
/libs/openssl/lib/libcrypto.a(cryptlib.o)
duplicate symbol _CRYPTO_set_dynlock_lock_callback in:
/proj.ios/frameworks/gpg.framework/gpg(libgpg.a-i386-master.o)
/libs/openssl/lib/libcrypto.a(cryptlib.o)
duplicate symbol _CRYPTO_set_dynlock_destroy_callback in:
/proj.ios/frameworks/gpg.framework/gpg(libgpg.a-i386-master.o)
/libs/openssl/lib/libcrypto.a(cryptlib.o)
duplicate symbol _CRYPTO_set_locking_callback in:
/proj.ios/frameworks/gpg.framework/gpg(libgpg.a-i386-master.o)
/libs/openssl/lib/libcrypto.a(cryptlib.o)
Because...
Google play games services include openssl module, but it is partially.
Cocos2d-x demand method(openssl) is not include in Google play games services.
So google play games services and openssl conflict module.
Are you here solving this problem?
Related
I'm trying to publish a Chrome Extension in a Private Store and to propagate it with a Group Policy.
In order to do that I'm using the following references:
CRX Packaging
GPO Propagation
I'm 100% sure that the GPO is configured correctly (if I use the same GPO to propagate an extension published on the Chrome WebStore it works).
Unfortunately, both my private extension (line in the Configure the list of force-installed apps and extension section: [my_extension_id];[my_xml_url]) and the example extension (line: bcanfnleljfidkjhhfknjjiicdonddad;https://sites.google.com/site/pushcrx/privatewebstore/2hrtimer.xml) are not installed in the domain controlled machine.
My question is: am I doing something wrong or the Google Chrome Policies have changed and the examples above are outdatet?
Thanks so much,
Daniele
In order to publish, deploy and update a Chrome extension outside the Google Chrome Store you have to follow the guide below.
1. Architecture
Firstable it is necessary to define the CRX and XML names and the url where they would be deployed.
For what concerns this example:
the CRX name would be myCRX.crx and it would be deployed at the url https://my.server/resources/myCRX.crx
the XML name would be myXML.xml and it would be deployed at the url https://my.server/resources/myXML.xml
2. JSON Manifest
As specified in this link the update_url (where the update XML could be found) must be contained in the JSON manifest: in order to do that it is necessary to insert the following line into the JSON file.
{
[...],
"update_url": "https://my.server/resources/myXML.xml",
[...]
}
3. CRX and private key creation
The creation of the CRX and the PEM can be performed following this guide.
At the end of the process two files would be created (a CRX and a PEM): after that it is necessary to rename them to myCRX.crx and myPEM.pem, respectively.
4. Public key extraction
The extraction of the public key can be performed by executing the following command from the folder where the PEM is located:
openssl.exe rsa -in myPEM.pem -pubout > myPEM_pub.pem
After that a new file containing the public key (named myPEM_pub.pem) would be created.
5. Extension ID extraction
The Extension ID extraction can be performed following this guide.
In particular, it is necessary to download the extension_id.py file, copy it in the folder containing the myPEM_pub.pem file and execute, from the same folder, the following command:
python extension_id.py myPEM_pub.pem
Note: if you're using Python 3 you have to modify the line 94 of the extension_id.py file from
with file(first_arg) as f:
to
with open(first_arg) as f:
The command output would be the following one:
[...]
Extension ID: <myExtensionID>
[...]
6. XML file creation
In order to properly deploy the extension it is necessary to create the update XML file (named, in this example, myXML.xml).
In this case its content would be:
<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
<app appid='<myExtensionID>'>
<updatecheck codebase='https://my.server/resources/myCRX.crx' version='<myExtensionVersion>' />
</app>
</gupdate>
Note: it is necessary to replace the following entries with the right values
<myExtensionID>, output of paragraph 5
https://my.server/resources/myCRX.crx, defined in paragraph 1
<myExtensionVersion>, defined in the manifest file
7. Publishing
In order to properly configure the environment it is necessary to publish the CRX created in paragraph 3 and the XML created in paragraph 6 at the urls defined in paragraph 1.
8. Deployment
The deployment of the extension can be performed following this guide.
In particular, it is necessary to add to the list of the force installed app and extension the following line:
<myExtensionID>;https://my.server/resources/myXML.xml
Note: it is necessary to replace the following entries with the right values
<myExtensionID>, output of paragraph 5
https://my.server/resources/myCRX.crx, defined in paragraph
1
9. Update - CRX creation
In order to update the extension it is necessary to create a new CRX package, with an updated version number (in this example <myNewExtensionVersion>).
The CRX creation can be performed following this guide.
Note: in order to make this process work it is necessary to select the key myPEM.pem, created in paragraph 3.
10. Update - Publishing
In order to publish the update it is necessary to rename the CRX created in paragraph 9 to myCRX.crx and to modify the version number in the XML created in paragraph 6 (see below).
<?xml version='1.0' encoding='UTF-8'?>
<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
<app appid='<myExtensionID>'>
<updatecheck codebase='https://my.server/resources/myCRX.crx' version='<myNewExtensionVersion>' />
</app>
</gupdate>
After that, the last thing that has to be done in order to perform the update is the publishing of the CRX and the XML at the urls defined in paragraph 1.
On Access VBA, I get an error on Environ in this string:
path = Environ("Temp") & "\DOTS\"
The error I get is the following:
How can I know what is the missing library?
Visual Basic Editor, select Tools --> References.
See if there are references whose check box is ticked (they are listed at the top) that start with MISSING: . If so, look further down the list for the version compatible with your application (e.g. if is says MISSING: Microsoft Word 15.0 Object Library look for a lower # in your references list like Microsoft Word 14.0 Object Library)
Currently, I am in the middle of migrating my iOS app from api.parse.com to my own server. In the guide I am following, I am at the point where I need to test the app's functionality with a local Parse Server. Although, setting up a custom Parse Server requires having the latest Parse-SDK, and I am running an older version. I am trying to update my frameworks via CocoaPods. My Podfile is as follows:
# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'
target 'MYAPP' do
# Uncomment this line if you're using Swift or would like to use dynamic frameworks
# use_frameworks!
# Pods for MYAPP
pod 'ParseFacebookUtilsV4'
pod 'Parse'
#pod 'ParseTwitterUtils'
pod 'ParseCrashReporting'
pod 'ParseUI'
target 'MYAPPTests' do
inherit! :search_paths
# Pods for testing
end
end
When I try running the app, I get the following error:
duplicate symbol _PFConfigParametersRESTKey in:
/Users/ME/Library/Developer/Xcode/DerivedData/MYAPP/Build/Products/Debug-iphoneos/Parse/libParse.a(PFConfig.o)
/Users/ME/Library/Developer/Xcode/DerivedData/MYAPP/Build/Products/Debug-iphoneos/Parse/libParse.a(PFConfigController.o)
duplicate symbol _PFConfigParametersRESTKey in:
/Users/ME/Library/Developer/Xcode/DerivedData/MYAPP/Build/Products/Debug-iphoneos/Parse/libParse.a(PFConfig.o)
/Users/ME/Library/Developer/Xcode/DerivedData/MYAPP/Build/Products/Debug-iphoneos/Parse/libParse.a(PFCurrentConfigController.o)
ld: 2 duplicate symbols for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
I've been searching for something online to help, but nobody seems to be experiencing this problem. I think my case is unique, as I have yet to see someone who has two duplicate errors on the same symbol pointing to the same archive(libParse.a) with one shared file (PFConfig.o) and two differing ones (PFConfigController.o and PFCurrentConfigController.o). I've implemented a variety of solutions that would generally solve this "duplicate symbol" error, but I haven't had any success.
Things I have done:
Ensured that all manually added versions of these frameworks have been removed from the project.
Scanned the project directory up and down multiple times via Finder/Command Line/grep/find and could not find any duplicated frameworks.
Ensured I did not add any "import *.m" files accidentally.
Checked for red files/duplicates in the Frameworks folder as well as the "Link Library With Libraries" section of "Build Phases."
Checked my framework, header, and other linker paths and they seem to be alright. My "Other Linker Flags" contains "$(inherited)" and a -force_load call to a third party ".a" file for analytics.
Cleared ~/Library/Developer/Xcode/DerivedData as well as removed Pods/ and ran "pod install" multiple times.
I went on to investigate the problem in the Parse files. The only place where PFConfigParametersRESTKey is defined is here and here. This seems alright since one of them is preceded by the extern keyword(reference here). I tried messing with the source files a little bit by making this variable not static and also trying to rename one of them. Nothing worked. I cannot figure out where to look to fix this.. If anybody can shed some light here I would greatly appreciate it! Thank you.
The solution to my problem was to remove an -ObjC flag from the linker config. For some reason, -ObjC was not one of the entries in the Linking section of Build Settings. The way I found it was by going to Pods/Pods-MYAPP.debug.xcconfig, and manually removing the -ObjC flag from the OTHER_LDFLAGS variable.
Does anyone know how to package an app for deployment of a HTML/JS Metro Application outside Visual Studio. I keep hearing reference to a "Store" Menu Item, but I am using Visual Studio 2012 RC Ultimate Edition, and there is no such Top level Menu Item.
I've also tried using the command line tool with a given manifest file (the one built automatically within a build) to create an appx file, but get some esoteric error message at the end of the packaging.
Update: Command line error message
MakeAppx pack /d .\Release\AppX /p generic.AppX
The package path (/p) parameter is: "generic.AppX"
The content directory (/d) parameter is: ".\Release\AppX"
Enumerating files from directory ".\Release\AppX"
Packing 52 file(s) in ".\Release\AppX" (content directory) to "generic.AppX" (p ackage name).
Using ".\Release\AppX\AppxManifest.xml" as the manifest for the package.
Adding ".\Release\AppX\images\splashscreen.png" to the package as a payload file. Its path in the package is "images\splashscreen.png".
Adding ".\Release\AppX\images\logo.png" to the package as a payload file. Its path in the package is "images\logo.png".
Adding ".\Release\AppX\images\smalllogo.png" to the package as a payload file. Its path in the package is "images\smalllogo.png".
Adding ".\Release\AppX\images\storelogo.png" to the package as a payload file. Its path in the package is "images\storelogo.png".
.........{Cut for brevity's sake}.........
MakeAppx : error: Package creation failed.
MakeAppx : error: 0x8007007b - The filename, directory name, or volume label syntax is incorrect.
Update: Figured It out (Sort of)!
I dont know what happened, but I create a blank XAML/C# Metro App. When you right click on the project, you get a Store option. It still wasnt showing up on my HTML/JS Metro app project, So i created a clean HTML/JS Metro Project....and there it was, a "Store" Option.
So I opened my current, non-working project again, right clicked on the project and there it was, the "store" option. I don't know if this was a 2012 RC bug, but I will leave this question here just in case someone else runs into this.
it is under the "Project" menu.
like you had said, it might be a bug. VS2012 is still buggy at the moment.
I hit this issue too, don't know the reason, but file mapping works for me, try call:
makeappx pack /v /o /f mappingfile.txt /p yourapp.appx
Content of mappingfile.txt:
[Files]
"App.xaml" "App.xaml"
"AppxManifest.xml" "AppxManifest.xml"
"folder\file.ext" "folder\file.ext"
"***.***" "***.***"
Error 1 Manifest references file 'Bing.Maps.dll' which is not part of the payload. C:\Users\xxx\Desktop\xxx\Applicationxx\Applicationxx\Package.appxmanifest Application7
I added this into a existing Metro application and its giving me that error, anyone has solution to it?
Go to the properties of the project and under Build, you will see Platform Target. Choose either x64 or x86 instead of Any CPU and it should be solved.
~Guo Hong
To correctly reference Bing Maps for a Metro app...
Go to: Project -> Add Reference -> Windows -> Extensions
Now, select both the "Bing Maps for ..." and also "Microsoft Visual C++ Runtime Package"
If you don't select the 2nd package, things will seem to be fine until you try to actually deploy your app.