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.
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.
For some reason it asks me if I want a debug or release kind of project when I create it, so I can't just switch between those 2 in one project. Do need to have 2 separate projects for debug and release?
This stems from the way how CMake works (to be precise, how CMake works with Makefile generator): it requires separate build directory for each build type.
I'm not sure what you mean by "having 2 separate projects", but intended way to do this is to select Project -> Open Configuration... menu for your project, go to CMake tab, and then click + button to add another build dir. Then you configure new build dir with the build type you want.
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"
I have a project that doesn't use autotools, but has a Makefile which I run to build the code. This make file is run from within in a shell script. I have imported the project in eclipse, but I can't seem to run the shell script (Something like Ctrl + B to Make or add one of the Make targets viz., make all or make install).
Is there a way I can do this?
You can specify a script to build your project in Project Properties -> C/C++ Build -> Build Command -> Builder Settings.
You can uncheck Use default build command and specify yours (e.g. make all, make install or bash make_all.sh). Or you can leave the default build command (it must be make) and in tab Behaviour specify targets.
But before you should have imported your project Makefile Project with Existing Code.
Don't use Eclipse if you are using Make tools in the same project. Eclipse brings you some tools for project compiling, etc. that you already have with Make/Automake.
I am trying to compile a VB6 project. On the File Menu it use to display MAKE PROJ1.EXE. Now it displays MAKE PROJ1. (note EXE is missing) The program runs fine in the IDE. I can start with full compile. I can even create a set up disk from the packaging and deployment wizard. I have a sucessful install, but the package will not run. There is no exe file. Other vb project compile just fine. Can anyone lend a hand????
That's weird
Open up the .VBP project file using Notepad and verify the following entry is correct
ExeName32="PROJ1.EXE"
Try this:
Right-click on VB6 toolbar
Customize
Make some change
Reset
Close
Make ... .exe
After that, it should work.