When trying to develop a cross platform GUI application on Windows, it seems whenever there's an error, the problem just closes with no information on what's wrong whatsoever.
How do i get my error messages?
You could try running it from the command line. Or change the compiler options for the project so the Compile Target is Executable instead of Executable with GUI, which should run it with a command prompt.
Related
Our projects all use CMake, and Fabric seems to require a script run in XCode's build environment to extract information. CMake doesn't seem to have a way to add a run script build phase.
So, I tried running the script manually after setting the following manually from known values in CMake:
INFOPLIST_PATH
BUILT_PRODUCTS_DIR
DWARF_DSYM_FILE_NAME
DWARF_DSYM_FOLDER_PATH
PROJECT_DIR
As a result, there were no errors when running the script but ..also nothing happened. I just got a "Launching uploader in validation mode" and then the process exited.
Is it possible I could get a full run-down of what the program needs in order to run? Our projects are built on a build server so having to VNC in and launch xcode to build is not really an option.
Thanks in advance.
Since you're using CMake, instead of using the run script build phase, I'd use the upload-symbols script as that will be a more reliable way to upload the dSYMs to Crashlytics.
I try to run a program which was build upon PowerBuilder version 10.2.1.9637 on a Windows 10 computer. After startup it shows an error message:
Error loading library. Please check whether PowerBuilder Accessibility library can be located in the path.
Doing some research I found out that there is a pbaccess***.dll needed to get the program run under Windows 10. However, is there a way to get this .dll since I do not own this specific version of PowerBuilder?
Or are there any other workarounds to get the program run?
This is from an earlier build of PB 10.2.1, but you can see if it works.
https://drive.google.com/open?id=0B6J5FirdQZquUFgwVmdkb1QtT28
You would have to get pbacc100.dll from the application developer. Alternately you can disable accessibility in control panel.
Somewhere along the line in the last week, Xamarin on my Windows machine started giving the above mentioned error any time I compile with MONO.
Specifically occurs when Project|Active Runtime is MONO - never happens when runtime is Microsoft.NET.
I've tried uninstalling/reinstalling MONO runtime (mono-3.2.3-gtksharp-2.12.11-win32-0.exe)
Any clues? Google searches come up with pretty much nothing
I get the same error today, (after an update yesterday to 4.2.4 Build 35) There is a bugfix here
Build works fine on another PC without the latest update (4.2.3 build 59). I guess the answer is to roll back to 4.2.3.
You can get it from your account page at Xamarin.com >> Downloads >> View all versions.
The solution from here says that you should either uncheck the box "Use MsBuild" in project settings or use .NET for building but then run with Mono if you want to test runtime compatibility.
I was using Flash builder for force .com IDE for my project but it has been expired.
Can I only use its SDK which I think should be free and compile my application using command prompt.
I know how to compile mxml applications from command line in simple flex application but for Force.com projects I am stuck.
I have copied all the swc in libs folder.
The compiler throws an error 'Error: could not resolve 'flexforforce:F3WebApplication' to a component implementation. '.
Can any one help me here? I don't know how to proceed from here :(
Thanks in advence.
You can see the true command-line parameters with the -dump-config option (see http://cookbooks.adobe.com/post_Compiling_Flex_libraries_with_Ant-16504.html)
Cheers
I'm not that up on VB.NET, the application I'm working on was not written by myself.
It works fine through the IDE but once I run it from the exe it gives me the above error.
Any clues?
This is really hacking me off!
The only user defined break point that I can think of is
Debugger.Break()
So, I would suspect that the .exe is compiled in debug mode. I would recommend Reflector to look at the code and find out for sure whether or not there is a Debugger.Break() somewhere in there.
Afaik, the only way this could occur if you are compiling under debugging settings. You should be able to fix it by doing the following:
Right-click your solution on the
solution explorer.
Select configuration properties.
At the top of the dialog box there should be a
combobox, which will most likely say
"Active(Debug)".
Click on the dropdown and select release.
Ok out of everything.
Build > Rebuild Solution.
Source: p2p.wrox.com
I believe the exe file was compiled using the "Debug" setting. Try changing the Build setting to Release and do a full build (rebuild) of the project. Then try to run the executable file. It should then run normally.
The reason you see that error is because when you normally compile and run applications in Visual Studio, it compiles a Debug build of the executable. The different between a debug build and a release build is that the debug build has additional information added to it, by the compiler, so it can be debugged properly.
I would suggest looking for stop in your code. That is what generated this error for me.