Android SDK : main.out.xml? - android-2.2-froyo

Sometimes Android SDK compiling Project will generate an empty layout XML named main.out.xml, which makes compile failed.
The file has to be deleted before compiling again. Why will it appear? and how to avoid it?
My IDE is Eclipse with ADT.

It was reported as a bug. There might an issue with xml plug-ins or something. I've always deleted the xxxx.out.xml file. Take a look at SO threads:
Eclipse - Disabling compiling of XML files while in Java perspective
android sdk main.out.xml parsing error?

Simply open any of the .java file in the src directory. Simply click on it an hit run

Related

Linker error building Adobe DNG SDK on MacOS 11

I am working on a project that uses Adobe's DNG SDK 1.6 library, and it is supposed to work on Windows and MacOS.
The library has instructions on how to build it for both platforms, but I had to figure out an error that came up on Windows with Visual Studio. I am not very experienced with big C++ projects so it was not trivial but I got it working. Most of my own code will be done in C# .Net Core, calling the native libraries using a wrapper class with P/Invoke.
Now for Mac that's a different story, I have a MacOS 11 VM, installed Xcode 12.5.1 and followed the steps provided, as expected, it does not work. Bare in mind this is my first time touching Xcode and MacOS.
The project I am trying to build is dng_validate, and it depends on two libraries built by these projects: XMPFiles64 and XMPCore64.
The library projects build without any hiccups, each one of them creating a ".a" file in the folder: dng_sdk_1_6/xmp/toolkit/public/libraries/macintosh/intel_64_libcpp/Debug, they are named libXMPFilesStaticDebug.a and libXMPCoreStaticDebug.a respectively.
When I try to build the dng_validate project, I get the following error:
Library not found for -lXMPFilesStaticDebug
Because of the the error starting with an "l" instead of "lib", under both libraries project settings, I changed the "Executable Prefix" setting to "l" instead of "lib". Rebuilt both of them and made sure the file names changed as expected. But the error persists when trying to build the main project.
Under dng_validate's project settings, there is a setting called "Library Search Paths" and it does point to the proper aforementioned folder using a relative path. I even changed it to an absolute path to see if that would make it work.
I am really lost here, does anyone have an idea of what might be causing it?
Well... After asking on other forums and almost hiring a freelancer to fix this for me, I tried another shot in the dark of renaming the library files and it worked.
I changed the extensions of libXMPFilesStaticDebug.a and libXMPCoreStaticDebug.a from ".a" to ".dylib" and it just compiled and blew my mind with it.

Incorporating charls into a MacOS application

Charls is an implementation of the JPEG-LS lossless and near-lossless coder/decoder. I downloaded the source code, built it in Xcode, and ran it on MacOS. From a few tests I ran, it seems to be reliable and very fast.
Now I want to incorporate charls into my application. I added the static library libcharls.a to my Xcode project and added the header file charls.h. When I try to do a build, I get the error: library not found for -lcharls. I then added a path to libcharls.a in the Library Search Paths of the Build Settings for the Project in Xcode. Still get the same error. Anyone have suggestions for getting this to build? TIA.
To answer my own question: adding the path to libcharls.a in Library Search Paths does fix the problem, but you only add the path, but not the file libcharls.a.

WebStorm 2016.1 TypeScript "Cannot start compiler process"

I've just installed JetBrains WebStorm 2016.1.1 Build #WS-145.597 for evaluation on OS X latest.
I want to use TypeScript but there is an immediate problem: I have enabled the TypeScript compiler in settings but in the Typescript Compiler tool window is complaining that it "Cannot start compiler process".
I've noticed that the build date on the WebStorm About box was yesterday (March 30 2016) so this may be a recently introduced issue.
Is anyone else having this problem? Anyone got an idea how to sort it?
Setting the TypeScript compiler alone didn't solve this for IntelliJ IDEA 2016.2.1 on Linux. I had to go back through my older project that didn't have the problem to find the solution.
After setting up your typescript compiler below.
I then had to directly edit this same setting within my project's .idea directory. Within your project structure, navigate to your .idea directory then locate and open file typescript-compiler.xml like below.
Now add the following xml option element after the "useConfig" option element:
<option name="nodeInterpreterTextField" value="$PROJECT_DIR$/../../node/bin/node" />
Be sure to change the directory path to your instance of node.
Sadly, this solution we be overridden every time you edit and save your settings. IDEA will have to fix their bug for a lasting solution.
I think you need to specify a node interpreter in the typescript settings:

DSFML building error (VisualD)

And at first, sorry for my bad English. It is my first project in D. And my first project with SFML (DSFML of course).
I use dub for making Visual Studio project (I use VS2010). Then
open it and set up project settings:
general
compiler
linker
Autocomplete works correctly:
When I try build project, here is error:
Error 42: Symbol Undefined _D5dsfml8graphics12__ModuleInfoZ
How I can resolve it?
This particular error is saying that it can't find the actual D code for the library. It could mean that dub isn't grabbing/linking the source somewhere, but I've never used dub with an IDE so I can't be sure.
My suggestion to help you figure out what is going wrong and to fix this issue is to bug the maintainer (who is me, actually) on github by opening an issue about a lack of tutorials for the IDE's that are available to D right now.
If you want to get started with DSFML right now, however, you can sort of follow along with the command line tutorial and use that as a basis of figuring out what libraries need to be linked in, set up import search paths, etc.
Create project by dub init dsfml_test (where dsfml_test is our project name)
Add libs dependencies to dub.json
Generate Visual Studio project
Open project in Visual Studio
Open project properties
Enter path to directory where is placed dsfml lib files
Thats all. Now can add import dsfml.graphics, dsfml.window, dsfml.system; ...etc and build project.

How to use Mailcore framework in my IOS project?

i have download mailcore for iphone from https://bitbucket.org/mronge/mailcore/downloads .i have try to build it shows error as
No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=armv6, VALID_ARCHS=i386)
So i can't add this mailcore framework to my ios project .Please help me to find solution
For the benefit of other searching:
As of Feb 2013, this is no longer an issue. MailCore download includes all libraries you need.
There are two issues I ran into, though, which sent me searching here for answers...
You have to have the command line tools installed in Xcode to build. The subprojects under MailCore use them to build themselves.
Xcode > preferences > downloads > components tab > Command Line tools must say "installed".
Subprojects under MailCore will throw errors about "config.h not found" if your path to MailCore contains a space. I found a closed issue in the github issue discussion stuff abou this. Thus, "/usr/home/me/dev/MailCore" is fine... but "/usr/home/me/dev stuff/MailCore" is not.
For #2, put your MailCore download somewhere where there's no spaces in the path. you can drag the MailCore.xcodeproj into your project to add it no matter where on disk your project is located. Doesn't have to be in the same folder.
From the Getting Started documentation on the project:
IPHONE USE
MailCore has an included iPhone
target, but it requires some
additional compiled binaries (OpenSSL
and CyrusSSL). I am unable to
currently provide these, however the
company Remail is offering the
binaries and a compiled copy of
MailCore for the iPhone. Contact
Remail for more information:
mailcore#remail.com
It seems like you'd need to get those before building against the iPhone target.

Resources