I am able to successfully build my project in the workspace (.xcworkspace), but when I open the project (xcodeproj) and try to build it there I get errors. A screenshot of the errors is attached. I've tried updating pods, installing, etc, but still cannot manage to get past this. Any advice?
edit:
This project/workspace is cloned from a repo. Whenever I clone to a new folder, I update pods.
After that, I am able to run the workspace, but not the project.
This repo is used by other people but they do not run into the same issue as me, they are able to run the project. This leads me to believe this has to do something with my Xcode setup. I have tried reinstalling and whatnot but still no success.
Related
I'm creating a project in Unity Hub, but when I try to open it, it throws an error. This project simply does not exist in the project folder (because of the error and the error). Several times I checked the correctness of the path.
I've reinstalled Unity several times but nothing has changed.
MacOS, path is /Users/Apple/unity_projects. It exists and is listed in the settings.
I reinstalled Unity again and it worked. The only possible problem is a lack of memory, because I did the same thing as before
I have cloned my Liferay 7.1 workspace from my Github repository. When I try to get Assistance in Liferay IDE using Control+Space, I get error:
This compilation unit is not on the build path of a java project
This happens on the new module project created in the same workspace(that was cloned from Github).
But when I create/import module from my local workspace that was created by Liferay for first time, this issue is not there.
I feel like there is some extra workspace setting that I am not doing in my Github workspace. Like we had to create build.username.properties in the SDK folder for Liferay 6.2. Totally stuck and no solutions anywhere.
I tried fixing Project Build path and Project Facets but did not help.
The way you did it in your own answer obviously solved it. My take on this is: The problem was most likely the .project file, because it contains all the configuration that eclipse requires, and the error message you post is an indicator that eclipse doesn't know what to do with these files.
The .project file can be regenerated from gradle settings, typically by choosing "gradle / refresh" (from memory, from the context menu of the project/workspace in Project Explorer), which will read the gradle settings and apply them to the eclipse world. This might happen automatically, but it might also need some manual push - next time you might want to try this, because just copying random files rarely is a good idea. You might end up pointing to other directories far outside of your workspace, and wonder why a local change is not picked up.
There were some differences between the workspace that I imported from Github and the one that Liferay was creating on my local. I opened both the workspaces in Beyond Compare. Following are the files that had major differences. I made them same and it started working after Gradle Refresh in Eclipse.
liferay-workspace/gradle/wrapper/gradle-wrapper.properties
liferay-workspace/.project
liferay-workspace/gradle.properties
liferay-workspace/gradlew
liferay-workspace/settings.gradle
I'm somewhat new to Swift and to development tools in general. After researching a lot about a question I had, I finally decided to ask it here. I hope it makes sense and be useful to others like me.
I wanted to take a look at a project in github: https://github.com/jyoo980/crypto-exchange
I clicked "Clone or download" and then "Open in Xcode". After that is done, I quit Xcode and I navigate to the project folder in the terminal and do a "pod install", which runs without any errors or anything. I go back to Xcode and I see files missing from the workspace marked with red. And of course the build fails because of "Build input files cannot be found". Missing files in workspace Build input files missing
What I noticed is, in Finder, the files are actually in the project but they are in subfolders, instead of the Model group as follows: Finder project files
So my question is, why would the project be structured like this in Xcode? And why would it not work right away when I clone it from github? Could this be a CocoaPods problem? Of course I can go to the "red" files and specify their location in Xcode and when I point them the problem is gone, but I would like to understand what's going on here.
Thanks in advance!
I have reproduced the issue, you are correct. A cloned project should work right away. You should report the issue to the repo owner on github, or fix it yourself and create a pull request.
I was trying to clone a project in Eclipse and after copying it into the same directory, I got a lot of build path errors, even after deleting the copy of the project. So, I decided to back up the original project, delete it from the directory and try importing it again. However, when I try to import it I get a "Gradle build daemon disappeared unexpectedly" error. I have looked extensively on this and other sites and found no solution, I tried deleting the .gradle folder as well as several others, to no avail. Can someone please help me?
It didn't fix the problem, but I managed to find a workaround by creating a new LibGDX project with the same name and then copying the 'src' folders from each subproject into their respective folders in the new project. Their were still a few problems with the android version, but once I picked an android target and added 'gen' to the source folders in the build path, it worked.
I have a project I checked out with svn at work. It has the following associated with it in Package Explorer view of Eclipse:
project[trunk]
project-adhoctest[trunk/adhoctest]
project-jar[trunk/gazelle]
project-war[trunk/webapp]
Now I have a file in the project jar directory that I have put a breakpoint in. What is weird is that when debugger is launched, it always goes to the project[trunk]. This is really bad because I need to debug changes I make, not the trunk I checked out, but in project-jar.
The only other details is that I used maven to build dependencies when I imported this project. But, to make sure I did that right, I deleted everything and checked out this project again. Still same problem. I goggled quite a bit and asked others at work what could be going wrong, but haven't found a fix yet.
I use Eclipse Juno, 4.2.2
Thanks,
GeekyOmega
The problem is the build path was wrong, for me. It was looking at the entire workplace and choosing the trunk. When I re-installed eclipse, when I first ran debug, it asked me for the build path. I pointed the build path to the project folder project-jar instead. This fixed the issue for me.
You must go to run-->debug configuration and add the branch project in the Source tab