I have the source from an Eclipse project, and I need to import all of the build settings as well as the source into a new project so I can make some changes. The trouble is, when I go to build the project, Eclipse is calling the internal builder and NOT calling the Makefile from the previous project (which I have imported). The makefile contains some values in #define statements that need to be passed in on the command line.
When I go to change these options in Eclipse (by right clicking on the project and going down to "Properties" and then examining the "C/C++ Build" tab) they are grayed out!
If someone could help me out I'd greatly appreciate it.
Thanks all!
There is a folder called ".settings" under your project, copy this (and everything under it) to your new project, this is where all of the settings are stored. To see the folder, you may need to use the view menu (upside down triangle) in the Package or Project Explorer and remove the filter on the ".resources". For Package Explorer select the "Filters", in Project Explorer use "Customize View"
Related
I've built a small desktop application with which I am trying to use a Setup project to allow other users to install it. But whenever I run this installer, it does not produce an executable file. This is my first time making a setup project.
My solution contains two projects. One is the setup project which installs the primary output from the other project. The other project is a WPF App that consists of two xaml files, a xaml.cs file for each, an App.config file, and an icon. It also has a few dependencies including one Assembly, two Frameworks, and a handful of Packages. The app works exactly as intended whenever I start a Visual Studio debugging instance on either Debug or Release configurations.
I followed these instructions to build my Setup and deploy my app.
Whenever I ran the resulting Setup, it installed an XML configuration file, a JSON file, a main application dll file, and a bunch of dll files for my assemblies. I looked into some resources on how to run the main dll file properly, only (A) I'm completely stumped by everything I find on that topic, and (B) I would rather just produce an executable file anyway, since I intend for this Setup project to be used by other people and it would be inconvenient to ask said others to jump through the same hoops just to run it.
Why does my Setup project not produce a .exe file? I see that a .exe file is produced in my bin folder whenever I build my project (and this .exe works), so I would think the setup project should also produce one of those, but it doesn't. What am I doing wrong with my Setup project or anything else?
The setup.exe is a bootstrapper over the setup.msi. We can install the content using .msi or by running .exe which inturn runs /gets the data from the msi. To enable setup.exe building, go to solution explorer -> project -> properties -> prerequisites. check the check box on the top "Create setup program to install prerequisite components". apply and rebuld the project. A setup.exe bootstrapper will be created allong with msi.
Switch to Release mode, then rebuild your setup project. If everything went well (check the output console), you'll find an MSI file inside {setup project folder}/bin/Release
In "system file" from your proyect installer, you shoud to add in "Application Folder" the next source = PublishItemsOutpuGroup. In my case functions well.
Finally, I thought of moving my project from Eclipse to IDE to IntelliJ. So, I carried out the following steps:
1. Installed Codenameone plugin in IntelliJ.
2. Import existing project to IntelliJ. Now I project structure is as shown in the figure.
Here, CodenameOne-Project is the main project including source folders images and all. The common and barcode-common consists of java classes required for main project(i.e.CodenameOne-Project). So, I am able to import CodenameOne-Project in IntelliJ, and if I add other folder as module by adding dependency and all, it dont look like CodenameOne project anymore. I cant properly import complete project. Any help on this would be very helpful. Thanks
P.S: I want to maintain same project structure.
We don't support importing projects between IDE's as our project structure is IDE agnostic. The IDE won't recognize that and would fail. The right thing to do is create a new project with the same package name/main class name as your existing project then copy your src & res directories on top of the new project and copy codenameone_settings.properties on top of the new project file.
I'm using Intellij Idea 15.0.3. I tried to use it to develop a MEAN stack application.
I first File -> New -> Project -> Empty Project to create an empty project. Then in Intellij Idea's terminal I type npm init -y, a package.json is generated. However, when I tried to edit this generated package.json, a window pops up, saying: These files do not belong to the project, and asks me if I want to edit it anyway.
Also, after I edited the package.json, I run npm install in the terminal, a new directory node_modules is generated, but it's not shown in the Intellij Idea.
How can I add package.json and node_modules into project? Do I have to manually created file or folder through Intellij Idea project UI and give up using its terminal?
You need to create a new project from existing source so..
File->New Project - Select HTML5/Javascript application then select one of the options at the bottom with "Existing Sources" at the end of it, you then just specify the folder that it's already and in and you should be good to go.
I can't build my project.
I created a new CDT project in Eclipse Helios and told it to use existing source and makefile -- both, of which, appear correctly in the Package and Project views. The "Project" menu has both "Build All" and "Build Project" grayed-out, however, so it's impossible to build the project. "Build Automatically" is unchecked. During project creation, I told the wizard to use the Linux gcc(1) toolchain. I've been unable to find anything under Project->Properties or Window->Preferences that enables the "Build Project" feature. The Window->Preferences->Build display shows only one tab labeled "Error Parsers".
How can I enable the "Build Project" command?
When you uncheck the
Project :: Build Automatically
button, then it will show you the option to
Project :: Build All
This may not be related to your issue if you're using a custom toolchain....
My experience with eclipse is that it sometimes doesn't quite grok the context of the file in the current editor. Have you tried right-clicking the project and selecting build there? Make sure you choose the actual project and not a source file. Also, make sure your source file is recently saved.
Usually, after I use the method above then the correct "Run As" and "Build" options will appear regardless of the current active editor file. I have this issue with Java, JUnit, C/C++, etc with Helios on Linux.
I've discovered the cause of my problem: selecting the wrong "New Project" wizard. I selected the "Makefile Project with Existing Code" wizard because the source and makefile already existed. I should have selected the "C Project" wizard and told it not to create a makefile. The result of doing the latter is that the "Build Project" entry of the "Project" menu is not grayed-out.
Apparently, the "Makefile Project with Existing code" is a generic wizard rather than one specific to C/C++ projects.
I have a rather simple C project I compile with make that I would like to run and debug in KDevelop, but I can't get this to work. I have installed cmake and tried both to import an existing project and start a new (which insists on creating a main.ccp file), but no matter what I do all the menu options to run the program are greyed out.
How can I move this project to KDevelop?
Hiya, once you have created the new project by importing the custom makefile,
go to the Run Menu, Launch Configurations, then select the Global tag, then press the green plus sign +.
This will create a new launch configuration that you need to fill out with all of the correct executable paths and arguments and whatnot.
Once these are set, then the execute/debug options will ungrey out.
I had to figure this out today, was not obvious at all.