I know this has been asked for ImageMagick couple of times and many times for How to link stuff in VS but it seems I cannot link ImageMagick's libraries with my program in VS2013!!!
What is wrong with the way i am doing it!?
Include Directory Setting
Library Directory Setting
Library Setting
These codes compile fine under Unix-Like environments, but not windows'.
I have been on this for whole day, any help would be appreciated.
Try adding
CORE_RL_MagickCore_.lib
CORE_RL_Magick++_.lib
CORE_RL_MagickWand_.lib
Instead. This works in my visual studio 2013.
Other than this I can see no other reason why it shouldn't be working.
Related
Visual Studio 2019 stopped to suggest Unreal Engine 4 libraries. It used to suggest the names of the heather files I could include in the "name_of_the_new_class.h" file. It used to look like this:
desired state (not my personal screen but that how it used to work), now I get this current state. I reinstalled UE4 and revalidated Visual Studio how do I solve this if that issue is even solvable?
Manually typed in header files work and it will compile and work but why IntelliSense is not suggesting me this .h files?
Using <> instead of "" works and autocompletion works again.
https://caligari.dartmouth.edu/doc/ibmcxx/en_US/doc/complink/tasks/tuinclud.htm?fbclid=IwAR1YfI-BL1Ub8MW5GRVDV2iafLhaJx086d9IL_mn3XZVCbD0GRSzqAZ1MCw
I have been trying to open x264 code base in Visual Studio, by creating a separate project for it, but without any success.
I thought it should have been straight forward. I could build X264 code using MinGW, but I need to edit the code and extract motion estimation code.
Has anyone compiled/run the x264 from Visual Studio?
Thanks!
Someone has done the job. They maintain a fork with a proper visual studio project
http://siliconandlithium.blogspot.ca/2014/03/building-x264-on-windows-with-visual.html
At the time this answer was written, there were no support for building x264 with Visual Studio.
Instead you should build it with MinGW/gcc or Intel Compiler. For instance, there are some howtos around - take a look here and here.
For me, the second method has worked out.
This is a new one for me. I have been asked, for legal reasons, to setup a laptop with Visual Studio, but to disable the ability to compile projects/solutions. The purpose is to enable browsing of the source code, but not allow building or executing it.
Yes, I know this is really a stupid question and unfortunately I can't get into too many details. I've asked about using alternative text editors, but I have been told no. So until I can prove it isn't possible (or that I have at least made a reasonable effort), I have to try and make this work. Notepad++ would be an excellent alternative, but that has been rejected.
This would be in Visual Studio 2010 or later. Is there any way that I can do this?
UPDATE
After trying Marius Bancila's suggestion of removing the compilers and MSBuild, I was surprised to find out that VS continued to work fine (except for building, of course). I did not expect that functionality like F12 (Go To Definition) would continue to work.
This may mean that there still remains the ability to build something somewhere somehow. But as it stands with MSBuild permanently deleted and the Visual Studio Build command not working, it'll take some effort to get around it (if a way in fact does exist).
You didn't say what projects should not be possible to build (VC++, VC#, VB.NET, F#, etc.). Starting with VS2010 they are all built using MSBuild. So if you delete MSBuild they will not be able to build from inside Visual Studio. However, one can still be able to build from the command line, so the only possibility I see is that you delete all the compilers that come with Visual Studio.
It's a little bit crazy, but if you really have to ...
Try deleting some important binaries after installing Visual Studio e.g. linker (link.exe) and compiler (cl.exe).
Use a text editor instead. Notepad++ even comes with color syntax highlighting.
You cannot prevent people from compiling the code. Visual Studio Express is available to anyone, and the compiler can be executed from the command line, without Visual Studio's help.
I installed Visual Studio 2012 Express followed by the TypeScript plugin.
I launched VS and noticed that my .ts files are not getting any syntax highlighting.
I did not have any of the project templates relating to TypeScript, nor the Tools->Options->Text Editors->TypeScript settings.
I even tried to uninstall/re-install everything. Nothing worked.
I was desperately looking for a solution and it seems like none exist, so I decided to post the solution that worked for me.
It could be a complete fluke, but I thought I'd share it anyway, in case it can help someone else.
I have Windows 8 installed, but I don't think that's a factor since my other PC works just fine with Windows 8 + VS 2012 Express + TS plugin.
I went into C:\Program Files (x86)\Microsoft SDKs\TypeScript\0.8.0.0 and with VS closed, I ran the TypeScriptLanguageService.vsix file.
HTH
You did find the appropriate work-around.
One known issue with the installer is that if your "documents" path is on a network share, the VSIX doesn't get installed automatically. Is that the case for you?
I've just attempted to use Firebreath and have followed their video tutorial for Windows and come across the error that says:
Check for working C compiler using Visual Studio 10 -- broken
And then says:
It fails with following output:
Change Dir:
And then lists the drive. This happens when running prep2010.cmd. I have found a post about it, but the forums won't let me log in and there is no answer. It's here: http://forum.firebreath.org/topic/274/?page=1#post-1117 and is exactly the same error, I believe. The last post talks about running prep2010 from inside the vs2010 command shell. What does that mean?
Has anyone else had this error or know how it is caused? I have no idea how to approach it.
Thankyou
I know this is really old.. but in case someone else has this problem, the solution for me was to install service pack 1 for visual studio 2010
As I said in the comment above, this is not "FireBreath" that is saying your compiler is broken; the prep command uses CMake to generate the project files, and it is from cmake that the error comes.
In your start menu where Visual Studio 2010 is there should be a "tools" or "utilities" subfolder and in there somewhere there is a "Visual Studio 2010 Command Prompt" link. That starts a command prompt with environment variables and path set up so that the vs2010 commands are all available. The error you're seeing is indicating that for whatever reason, CMake is unable to find visual studio 2010.
I don't know if using the vs2010 command prompt will help or not; it doesn't have any trouble finding vs2010 on any of my boxes. I can postulate that perhaps if you installed it to a nonstandard location, in a nonstandard way, or your registry got screwed up any of these things could potentially cause the issue that you are seeing. Also if you don't have vs2010 installed it would certainly cause this issue =]
I'd recommend first trying the vs2010 command prompt; if that doesn't work, you may have to try uninstalling and reinstalling vs2010. If that doesn't work, I'm out of ideas, and maybe someone who knows more about cmake will have a suggestion :-(
Service pack 1:
http://www.microsoft.com/en-us/download/details.aspx?id=23691
Configure cmake with generator: MSVC2010 x64
I also had MSCV 2010 x64 on windows 7 and installing service pack one also helped.
Also make sure that all your external dependancies are (x64) versions:
MSVC version:
http://visual-studio-2010.en.malavida.com/
Gl&HF