I've never spent so much time on initial setup for a development environment before, this is getting kind of ridiculous.
I'm trying to run the demo code that comes with cocos2dx.
I'm using:
the eclipse flavor that comes with the ADK.
cocos2d-2.1beta3-x-2.1.0
ndk-r8c
Ive tried building an app template using create-android-project.sh which I had the same problems with but for this question I'll reference the hello.cpp sample app.
I run the build_native.sh script and then import it in eclipse.
Next is where all the different tutorials I've tried vary. Some say to 'convert to a c++ project' some say you can already 'run as android project' at this point already.
For me it seem like the android java project can't link to the cocos2dx project.
I get:
The import org.cocos2dx.lib cannot be resolved
for
import org.cocos2dx.lib.Cocos2dxActivity
No tutorial really made any mention of having to build the cocos2dx libraries except for one that said you now have to import the cocos libraries as projects in to the eclipse workspace. So Ive done that and built them but there are some errors in them after building.
I've also tried adding the folder path to link to in the project which for me is at /cocos2d-2.1beta3-x-2.1.0/cocos2dx/platform/android/java/src/org/cocos2dx/lib but that didn't help.
Any idea why I can't build/run the examples that come with cocos2dx even when following the build instructions that are on the cocos2dx website to the T?
I'm doing this now on OSX as well and this fixed it for me:
run the adroid script create-android-project.sh then
import that new project into Eclipse
in the new Eclipse project right-click the src folder > left-click 'Import'
in the Import window choose Android > Existing Android Code Into Workspace > Next >>
Browse to '/cocos2dx/platform/android/java' ('/cocos2dx/' should be be one level above the new project's directory)
click Finish. If the error persists try a Project > Clean
Related
NetBeans run programs and create project normally, but when I try to open an existing Project it doesn't recognize the project folder so when I click "Open Project" it doesn't open it.
it works fine using intellij IDE but I need To use NetBeans .
I tried using Import Project But the Same problem.
when I try to Import it it gives me an error :"C:\Users\ahmad\OneDrive\Documents\Desktop\ch24" does not contain a regular Eclipse project."
I uninstalled NetBeans 12.4 before installing NetBeans 13 if this may help.
When I try to open project:
1)
2)
I read on the internet I should change NetBeans.conf file Java home, but it was the right path already.
3)
I searched on the internet but found really old posts (9 years) and didn't work with me, such as changing java home path in netbeans conf. Using import Project.
Tried Moving the folder to NeatBeans Project folder but the same problem.
I would like to use the "Play" Framework on the IDE Eclipse for the first time. Therefore, I have downloaded the Java starter project.
The problem is that, when I try to import it on Eclipse (File > Import > Existing Project into Workspace), I have the following error message "No projects are found to import".
I think it is because I haven't compiled the project and also because I do not have a .project filetype in my directory.
But when I follow the tutorial, it does not work (even though I have tried to do it very carefully). I have spent 9 hours on this problem, I am rather new to programming, and I would appreciate your help. Thank you in advance.
The project is a gradle project so instead of importing it as existing project import it as a gradle Project
I am importing the following project : ActionBarCompat-Basic from the Android Developers website into Eclipse.
by doing so: File -> Import => Android existing project.
However, in my package explorer, it creates me two projects :
1) The first project is named MainActivity
2) The second project is named tests.
Also, the two projects both have errors
Is that normal ? If yes, how can I solve the errors issue ?
Note, because you do not say wich project you are importing, this a blind answer.
You get two project simply because in the downloaded folder are two project.
To resolve errors first of all try to do a clean Project=>Clean... and select the projects you want to clean.
Unfortunately errors are common when you import project coming from around the web.
You should right click those projects, open Properties and check the Android tab, check if you are missing some library and try to figure out wich library is (or are).
Check Android 4.4.2 as build target.
Open the Java Build Path tab and open the Source tab, check if the gen and src folders are there, if not, add them.
If error are still there open the files marked with the error icon and try to figure out wich library they miss.
Check the Eclipse error Log.
I hope this help.
I use IntelliJ IDEA 12, Play 2.2.0, I have Scala plugin installed, Play 2.0 support plugin installed.
I created java play application via termina (play new). Andas you can see in this pictures I always get this error: "cannot resolve method ok()" or "cannot resolve symbol at"
http://sluchatka.kvalitne.cz/pics/1.png
http://sluchatka.kvalitne.cz/pics/2.png
I searched the web for this problem the whole day, but I didn't find solution.
Can you please help me?
The first problem (unable to resolve reference to template) is because your template probably has not been compiled by the moment (and thus IDEA does not see compiled template and can't resolve reference to it).
I usually develop Play apps having ~run command launched in Play console. So that any changes to templates are immediately compiled and changes detected by IDEA.
As for the second one it seems like a deficiency in Play IDEA plugin. It does not work seamlessly within templates I should say. Lots of glitches. The best way I found is to have ~run launched so that small problems are detected immediately.
According to intelliJ support it is better to import the command line created play 2 project using the IDE import project wizard instead.
File -> Import Project
Select play2 project location
Import as SBT project
This was due to the "play idea" command being outdated or not fully compatible with the current play 2 and scala plugins for intelliJ.
A bonus is that errors start to appear properly, we had trouble with that earlier.
I was having a similar issue with Play 2.4.2 and Intellij 14.1.4. I could run the basic "play-java" example/starter app in Intellij, even though the editor showed errors like "cannot resolve method ok()".
Here's what solves the problem for me:
Before starting, make sure your project is not open in Intellij.
Delete the ".idea" folder from your existing app, OR just create a new app using "activator new".
On the command line, cd to the app's folder and compile using "activator compile".
In Intellij, File -> Open, and select your app's folder. For the SBT import options, I left the boxes unchecked (e.g. "Use auto-import", "Create directories for empty content roots automatically", etc.) but I don't think it matters.
Once everything finishes loading, you shouldn't see the errors any more.
This click in the Project Structure is your answer.
I have been working as a programmer for approx 15 years. I have significant experience with 3 languages. Object Pascal, C# and Python. I just took a job (like two days ago) as a project manager for a Java project that has been written with the following tech stack.
Java EE
Eclipse Helios
Tomcat
Spring
MySQL
Code is in SVN
In preperation of starting the job, I read a couple of books on Java and played around with eclipse. The language doesn't bother me at all - it's very similar to C#. What I'm really struggling with now feels more like how to get started.
I've sync'd the code from the SVN repository, but literally am not sure how to proceed. I think I'm use to having solution or a project file to "open" (like in Delphi and Visual Studio). So, do I need to create a new workspace and "import" it from the file system?
I apologies for the newbie questions. I just feel a bit lost getting started here. Maybe someone that has recently come from a Visual Studio background can sympathize with me situation! :)
Thanks in advance for your help.
Well, it depends a bit on how your company's SVN is organized. For example, do they check in the Eclipse project settings, or do they expect you to check out the code and then generate Eclipse settings? Both are common approaches.
Assuming they have project settings in SVN, you should be able to just import them. You can either directly import from SVN as a new project (using the Eclipse new project wizard), or you can check out the code from SVN with an external tool (e.g. Tortoise) and then use Eclipse's import wizard to import the project. Go to Import -> General -> Existing projects into workspace, then browse to the location of your SVN working copy, and it should automatically pick up the Eclipse project(s) there.
update following up on your comments, let me expand a bit. Say, you check out a working copy from SVN using Tortoise, for example to c:\foo. You can then import any projects in that working copy into Eclipe, using the "Import existing projects into workspace" option I mentioned above. In the import wizard, you can choose if Eclipse should copy the actual code into its workspace directory, or should leave it where it is and just keep references. This is personal taste but I usually do not let Eclipse copy the code into its own workspace. That way, I can work with the code in Eclipse (and do SVN updates/commits directly from Eclipse), but also can quite easily do operations on my svn working copy outside Eclipse.
A workspace in Eclipse can contain multiple Projects.
When you open eclipse it has you select which workspace to use, and then you should be able to import the code into eclipse as a new Project. Have you tried using the Project Wizard?
You won't find an exact equivalent of the .csproj file, the closest you get is the .project & .classpath files, between them eclipse has all the information to describe a project. If your svn checkout contains the .project file, you can directly import your project into eclipse using the Import Wizard. Else you can try creating a new project and pointing it to your svn checkout.