I am here with a newbie question. I have just installed codeblocks. When I tried to run a simple hello word, I had the warning of "Linker input file not found." How can I solve this problem? Thank you. enter image description here
Have you modified the project?
Lets try to fix it:
Project->Properties->Build targets->Build target files -> Is main.cpp checked?
Have you tried a new project? Without modification?
Does the path to your project has special characters, like non English or spaces?
Have you tried a rebuild: Build->Rebuild?
Related
I am creating an apk in Sketchware. I am trying to create a .db file editor, but this apk requires me to create a file manager within it so that I can browse the .db file. I was guided by this tutorial: https:/ /youtu .be/OkiBwSrT5WY
But when compiling in my project it gives me an error
enter image description here
Error in /storage/emulated/0/.sketchware/mysc/602/app/src/main/java/com/DbEditor/VictorChannel/PageEditActivity.java (at line 83)
","design"));
Syntax error in token "","", #expected
Error in /storage/emulated/0/.sketchware/mysc/602/app/src/main/java/com/DbEditor/VictorChannel/PageEditActivity.java (at line 83)
","design"));
String literal is not properly closed with a double quote
I tried to look in the code what the problem was, I tried to remove the quotes, it didn't work, then I removed the parentheses in the code, that didn't work either.
It doesn't work for me when trying to compile the apk directly from Sketchware it puts back quotes and parentheses it seems that it doesn't change anything.
enter image description here
I don't know what to do please
Can someone please help me?
((View)_toolbar.getParent()).setBackgroundColor(Color.parseColor(_c));
getSupportActionBar().setBackgroundDrawable(new android.graphics.drawable.ColorDrawable(Color.parseColor(_c)));
Hello to whoever reading this.
This is not actually a question. It's a problem i faced and i was trying to find solution here in stackoverflow. But i couldn't. [Chances are it may be duplicate in the eyes of experts]. Anyway thought i'll share the solution which is working for me.
The Problem
I work on Windows CE panels so in some scenario I need to read batch script variable in CMakeLists.txt to do some filtering based on whether it's Windows x86 or Windows CE. How to do that ?
Could be the same as This but for me export didn't work. So the whole picture.
Later checked export is in bash. In batch set will work
The Answer which is working for me. [There are chance that other solution also exists but this worked for me]. Ok here it goes.
In batch file
set "PANEL_TYPE=WINCE"
In CMakeLists.txt
if( $ENV{PANEL_TYPE} STREQUAL "WINCE")
message(STATUS "Print Message = " $ENV{PANEL_TYPE})
set(THE STUFF)
else()
message(STATUS "Other Message = " $ENV{PANEL_TYPE})
endif()
That's it. It seems simple to me and it worked :)
I'm trying to localize my app, and I have the following code:
self.arrayLabels = [NSArray arrayWithObjects:NSLocalizedString(#"This is a test", "this is a test"), NSLocalizedString(#"I want my strings to get added to localizable strings file", "strings comment") , nil];
So, basically, from what I understand, this should be it, I click Editor > Export for Localization and the strings should be there on my XLiff file. But, they aren't.
I have two languages, english and portuguese, both localizable.strings files are empty.
Am I missing something?
I discovered that I had a few errors and that is why I could not export from the menu.
I suspect that the error messages are not being returned.
It turns out that the menu is calling existing command line tools so by a process of elimination you may be able to fix your export.
Here are the steps I took to fix my issues. Hopefully they will help you.
Run the command line equivalent
xcodebuild -exportLocalizations
If you have errors xcodebuild may give file names and line numbers so you should be able to fix the issues.
I had one error that did not have any details.
I then switched to using genstrings as that is what xcodebuild appears to be using in a loop.
find . -name '*.m' | xargs genstrings -o somePath/en.lproj
this gave the same error
To get the file with the problem I ran each file separately in a loop.
for f in `find . -name '*.m'`; do
echo "processing $f ...";
genstrings -o somePath/en.lproj $f
done
That gave me the name of the file that had an issue.
It turned out that genstrings did not like a special character I was trying to print using a unicode character \U000000B2.
For the exported XLIFF to contain your localized strings, a few conditions have to be met:
The keys must be present in your localized strings file. In your case these files are empty. Which will explain the problem.
You must use the keys as string literal with the NSLocalizedString macro. For example:
This is the correct way:
NSLocalizedString("some_key", "")
This will not work:
let key = "some_key"
NSLocalizedString(key, "")
In Xcode, use the Editor-->"Extract for Localization" menu which will generate the .xliff files (one per language selected). The .xliff files are sent to a translation service for translation. Once the .xliff files are updated by the translation service, you need to import it back into the app using Editor-->"Import Localizations". Once this step is done, for each language, you will find a xx.lproj/ folder with the results of the translation.
So I am trying to compile Pascal programs and everything is find; however, I would like to put the generated files after each compilation is a separated folder. I am looking of something like this: fpc "Destination Folder" "program.pas".
Thanks
From Alphabetical listing of command line options
-FE<x> Set exe/unit output path to <x>
-FU<x> Set unit output path to <x>, overrides -FE
So something like fpc program.pas -FEc:\output should work. I don't have fpc installed so I cannot verify. If you try it and get errors that you can't work through post them.
This one works for me:
fpc hello.pas -o"Web/hello.cgi"
I was using ubuntu, notice there is no space between the argument -o and the beginning of the path "Web/..."
I have added a include directory in my home directory. I can run "ls -l ~/include" from the build directory.
I have added that directory in both "Header Seach Path" and in "User Header Search Path". In both places I have tried with both non-recursive and recursive.
But xcode 4.5.1 can not in any situation find the first stated header file.
It is stated in source code calls.m as:
#include <directory/file.h>
I get a "Lexical or Preprocessor issue 'directory/file.h' file not found."
But when running xcodebuild from cli it has no problems what so ever to build the source.
I have tried many of the suggestions found on internet
Putting a include in /usr/ om my drive
Adding a index to the project, adding files with no copy and no "Add to target" marked.
Restart xcode.
Specifying all specific paths.
But still no go.
What is the problem. Bug´s in xcode?
I just had a similar issue, and it was because there were spaces in the path which I defined for the Header Search Path. For example, I was defining the following as a search path:
$(SRCROOT)/Frameworks/Headers
which was being expanded out to the following:
/Users/skoota/Documents/Xcode Projects/My App/Frameworks/Headers
as you can see, there are spaces within the path (which are not immediately evident, as you are using the $(SRCROOT) variable) and the compiler doesn't particularly appreciate the spaces. I solved this problem by changing the search path to this:
"$(SRCROOT)"/Frameworks/Headers
(note the quote marks around $(SRCROOT) which escapes the spaces). This now expanded out to:
"/Users/skoota/Documents/Xcode Projects/My App"/Frameworks/Headers
which works perfectly, although looks a bit odd with the embedded " marks. This took me a while to figure out, so hopefully it helps!
This usually happens if there are spaces in your directory's path. To overcome this problem, use double quotes around the path.
Suppose you want to use your project directory, then you should use: $PROJECT_DIR. Enable recursive if you want to search within the folders as well. Alternatively, you can use $(SRCROOT)