My code runs a previous version of itself, so even though i completely remove all the code, it still runs the old one. I've read a few other posts regarding this problem, and tried it out. My temporary solution is to build the project before running it, but that is kinda stupid. the .exe file is in the Release folder, and my Debug folder dissapeared after the Clean.
How do I stop needing to build the project before everytime I need to run it?
I found out there's a button called auto build in the Launch Configuration properties window. So it build everytime I run it.
Related
I am getting an Xcode build error after I deleted icomoon.ttf since I wasn't planning on using it any longer. How can I get rid of this annoying build error? App still launches and runs normally, though. I guess I need to alter my Info.plist file, but I don't want to mess anything up. Any ideas?
Open ios/<projectName>/project.pbxproj and Info.plist.
Find any remaining references to that font and remove them.
In Xcode run Product, Clean Build Folder
Restart JS sever, run build or react-native run-ios.
In Info.plist if you don't need any other special fonts you could remove the fonts key and the array.
I tested with a new RN Project, since I don't need any special fonts I don't have any UIFonts key in Info.plist.
When I use the "Start without Debugging" button in Visual Studio, my app is copied to a debug directory and runs from there, which I discovered via Environment.CurrentDirectory.
However, there is a text file in the root of the project that I also need to copy, regardless of the build options. When I press "Start without Debugging", this file is never copied, despite the properties set:
Can anyone please provide instructions on what options to include this file when starting without debugging?
Oddly enough, I don't have the "AdditionalFiles" listed in my WinForms app Build Action, also tried with VS2015. Though setting the Build Action to "Content" works for me, when doing the CTRL-F5.
In the very beginning, I created the AwesomeProject. Later when I use command
react-native init MyProject, it only created a package.json there. Before that, it could create other files, but very slow.
I searched some ways to fix it, now it only create one file.
It's a known issue that has been fixed (be sure to update react-native-cli): the command seems to hang forever nothing seems to be downloaded.
Try using react-native init MyProject --verbose to see what's happening and/or keep trying. The issue is not coming from your config.
So I am new to CDT (even though I have worked with C and Eclipse Java before), and seem to be getting the error as shown in the picture below:
Now, when I check the Run Configurations, the application field of the debug applicaiton seems to be empty, as shown below:
Finally, when I check the actual physical location of where the debug executable should be, the folder seems to be empty, even though I am going through the build process.
Does anyone know why this problem is being caused, and why exactly eclipse isn't building/compiling my executable?
NOTE : I am currently using Eclipse Luna.
It seems that your program doesn't compile correctly, maybe because you have a build error at the compiler level...
Try to press CTRL+B and see if in the problems section you get some errors of the compiler .
If you are familiar with developing Java in Eclipse, then you might have hit a problem that the default setting for Java is to continuously build. However for CDT you need to tell Eclipse to build the project. This can be done by pressing CTRL+B to build all projects in the workspace, or right-clicking on the desired project and selecting Build Project.
Once you have the first build of your project, future builds can be completed automatically by using the Build (if required) before launching option in Window | Preferences | Run/Debug | Launching as shown in this screenshot:
Once you do the first build and set up your launch configuration. Then the edit/debug cycle becomes very efficient, simply code and hit Run or Debug button when ready.
Im trying to merge 2 projects in visual studio and getting a LNK1181 error. I have searched on google and tried everything i came across but i simple cant solve the problem.
I am getting the following results:
Performing a build this succeeds.
Performing a Rebuild it fails with error LNK1181: cannot open input file 'a.dll'
Doing a build the output screen shows the dll is created and it is there in the folder.
Doing a rebuild the output screen shows the dll is created but then it is not in the folder. And then the rebuild results in the fail + the error LNK1181.
So what is wrong? What is different on a rebuild?
I can even see in the folder that the dll is beiing created and then removed again..
*I have 1 project that is the main project and creates the .exe, and it relies on a other project to run.
Solution:
I found the problem and is has nothing to do with the LNK error message i am getting.
Apparently a clean -> build is very different from doing just a rebuild. Mainly because i have multiple projects. When doing a clean -> build is first cleans all the files and then builds all the projects.
But doing a rebuild project A is beiing cleaned and build, then project B is beiing cleaned and build etc..
This way the lib generated bij A is beiing deleted. The solution for this is or just do a clean -> build. Or perform my own clean by deleting the files myself and then do a rebuild.
Also i dont feel like spending to much time on this issue when it is just a MSbuild "problem/bug" and doing a clean build is good enough.
linker error is maybe due to some lib is missing.
firstly check whether you have the lib for a.dll,
then add correct path for the lib in Visual Studio.