How do I set the output directory for a Build in Eclipse ?

I changed the directory structure above my project.

I can build the project, but the output files still go to old directory structure and the Settings Editor comes up with no settings for this project.

Where can I set the output for the project build so that it matches the new directory structure ?

Thanks

  • BTW, is there anything unusual in your monkey.jungle? You're not overriding base.sourcePath or any other .sourcePath, are you?

  • I haven't messed with monkey.jungle at all so it's whatever it defaults to when a project is created.

    It looks like I'm out of the woods.... at least until the next surprise.

    Creating a new workspace directory, then using "open project from file system" seems to have cleaned things up. I can now build the project for the two targets that I test with, run each in the simulator, and the simulator finds the required files and allows me to edit settings.... so I'm set until things go south again :-)

    I am pretty sure that your other approach would have worked also.

    Thanks again for your help.

    I really appreciate it.

  • When you were importing, did you have "Copy Projects into Workspace" checked?

  • Hi Jim.

    That option does not appear in the "Open Projects from File System" dialog that I got.

  • If you are importing an existing project, that's not the option you'd typically use. You use "existing projects into workspace".  Same as when you import a sample from the SDK.

  • To be fair, "Open Projects from File System" is readily available from File menu, right under "Open File". To me, that suggests that the devs want you to use this option for importing a project which is not already in your workspace.

    In order to access "Existing Projects into Workspace" it was several more clicks (at least for me):

    File > Open Projects from File System > Show other specialized import wizards > General > Existing Projects into Workspace

    or

    Right-click in Project Explorer > Import > General > Existing Projects into Workspace

    So if the latter is supposed to be the "correct way of doing things", it certainly isn't more obvious. I've actually always used Open Projects from File System without any problems. (If I want to copy something into my workspace folder, I do it manually.)

    According to Stack Overflow, the main difference is that Open Projects from File System doesn't require the .project file to already exist, while Existing Projects... does.

    https://stackoverflow.com/questions/64630761/eclipse-open-project-vs-import-project

    Import Existing Project imports a project from some other workspace and adds it to the current workspace. You can choose to copy everything in the project in to the workspace which makes it completely independent of the original project location, or you can leave the project pointing to original location.

    Some versions of Eclipse also have a 'Open Projects from File System...' menu item which is variant of the Import Existing Projects but supports finding projects in a directory or archive (jar or zip). This will try and guess the project type even without the .project file that identifies an Eclipse project and is required for Import Existing Projects.

    As you pointed out, there's also the "Copy Project into Workspace" option that only appears in "Existing Projects...". I don't see why you'd have to use that option in order to import something successfully tho, especially if you intend on leaving the files in the place that you opened them from.

  • See "Importing an example" in the doc:

    https://developer.garmin.com/connect-iq/connect-iq-basics/your-first-app/

    It's the same when you want to add any existing project to a workspace, be it a download or from a different workspace.