compilation

I hava small windows app where user enter code and on button click event code is compiled at runtime. When i click button 1st time it works fine but if click same button more than once it gives error "The process cannot access the Exmaple.pdb file because it is being used by another process." . Below is the example sample code using System.Linq; using System.Text; using System.Threading.Tasks; using System.Windows.Forms; using Microsoft.CSharp; using System.CodeDom.Compiler; using System.Reflection; using System.IO; namespace WindowsFormsApplication1 { public partial class Form1 : Form {

I've been trying to incorporate the lessc compiler in a large project that has the basic setup from Bootstrap and it only results in various compileerrors (for which there are tickets for everyone with different solutions). Not one solution give me what I want, which is a way to compile the less-pile through the command line. I compile various other assets through node.js and hoped to do the same thing with the less, but every googlepage I find on the subject is Node.js+Express which is not what I want. I want a standalone compiler. (Idea: require.js r.js-file) I found Node-less but it hasnt

I'm trying to compile my hello.pyx file to an exe using Cython. First step was to compile the hello.pyx into a hello.cpp file using command "cython --cplus --embed hello.pyx". Embed option means to Generate a main() function that embeds the Python interpreter . I'm trying to create an independent exe with no dependencies. In hello.cpp I have an #include "Python.h" , so I'm downloading Python sources from here: http://www.python.org/download/releases/2.6.6/ , choosing Gzipped source tar ball (2.6.6) . I add include dir and get error about missing Python26.lib. So I am trying to compile it. The

I use the command lines in Ubuntu's terminal. And I am trying to compile the three files presented in CUDA_Compiler_Driver_NVCC.pdf When I do use the command line given by the documentation on these 3 files, I do get the following errors: nvcc fatal : don't know what to do with'-dc' If I erase -dc in the command line, I do get the following error too: nvcc fatal : don't know what to do with'-arch=sm=20' Do anyone know how I could fix this issue ? Thanks a lot in advance for your help Gibo Below, you will find the command line I entered in the terminal, and the files. Command line used: nvcc

I'm a newbie to Linux kernel. I'm trying to understand the idea, high level what is kbuild . When I compile kernel I call make , which is on Linux machine will GNU make. So what is KBuild? Is it a set of makefiles which are used by including in kernel makefiles? Where kmk is used? Reference will be helpful. Thanks Dan Aloni The links you have mentioned have nothing to do with the Linux kernel. kbuild is an assortment of scripts that are built-in inside the kernel's sources, and the kernel build process does not depend on anything named kmk. The kernel build system depends only on the standard

I've been reading Eric Lippert 's article about the /optimize command line option of the C# compiler. The article describes what kind of optimizations the compiler performs. However it remains unclear to me if this option affects JIT optimization as well. It is not unthinkable, that this option would make the compiler to emit some metadata, that jitter can understand to change "optimization mode". Is there any reference that can confirm or otherwise if this option does indeed affect JITter? Bryan Crosby Is there any reference that can confirm or otherwise if this option does indeed affect

So I've got this example C program. int worship(long john) { return 0 * john; } int main() { return worship(666); } The assembly looks (essentially) like this: worship(long): pushq %rbp movq %rsp, %rbp movq %rdi, -8(%rbp) movl $0, %eax popq %rbp ret main: pushq %rbp movq %rsp, %rbp movl $666, %edi call worship(long) popq %rbp ret I ran into this while reading about stack smashing. In the assembly worship(long): section where it says movq %rdi, -8(%rbp) I would expect it to be using pushq based on everything I've read so far. Is this the new way that GCC is pushing arguments onto the stack and

I am running a simple Makefile with no problems: CC=gcc CFLAGS= -std=c99 -ggdb -Wall -I. DEPS = hellomake.h OBJ = hellomake.o hellofunc.o %.o: %.c $(DEPS) $(CC) -c -o $@ $< $(CFLAGS) hellomake: $(OBJ) gcc -o $@ $^ $(CFLAGS) The files are in the main project's directory: ./project/Makefile ./project/hellomake.c ./project/hellomake.h Then I tried to organized the files, and put things like: ./project/Makefile ./project/src/hellomake.c ./project/include/hellomake.h and extra subdirectories directories: ./project/lib ./project/obj Then the new version of the Makefile: IDIR =include CC=gcc CFLAGS=