tomlau10 / gcc-make-run

Compile-run C/C++ source code and execute Makefile in Atom.
https://atom.io/packages/gcc-make-run
MIT License
24 stars 10 forks source link

Unable to explain #11

Closed arjunkharbanda closed 8 years ago

arjunkharbanda commented 8 years ago

the current target is syswow64 make it `system32 as i am used to that after using sublime text3 also including the build that I used in Sublime text may come handy. and thanks for making this package in the first place will love to help but I don't have any knowledge regarding CSON/JSON C.txt C++.txt

tomlau10 commented 8 years ago

to build a 32bit target, you shall include -m32 in the compiler flags. hope this can solve your problem and you may close this issue afterwards or ask for further help. and thanks for using this package. :smile:

arjunkharbanda commented 8 years ago

Thanks

arjunkharbanda commented 8 years ago

not helpfull

arjunkharbanda commented 8 years ago

screenshot 8

screenshot 9 see this on Atom when I compile it is showing that datbase icon and on the other hand in ST3 it cmd in admin. please help make as same in Atom as I am so use to it.

tomlau10 commented 8 years ago

sorry I don't quite get the issue you mean that the cmd that this plugin invokes is shown as the database icon instead of a normal cmd icon?! i never come into this :fearful: can you provide more information? for example when right click on that database icon cmd, see what actual process and path is that executable?

and maybe my previous reply got your issue wrongly what is the original issue build target you mentioned about? by syswow64 and system32 do you mean 32bit 64bit build target ?

arjunkharbanda commented 8 years ago

capture capture2 sorry to confuse you but this is actual issue and here the info you want and syswow64 and system32 are target locations

tomlau10 commented 8 years ago

to spawn a shell, my plugin just invoke start cmd /c "command to run"

from your first figure, the comment Shortcut To C:\Windows\SysWOW64\cmd.exe seems to me that it somehow hides the original cmd command and invoke the StartDB.bat instead ...

perhaps your PATH environment variable priority has some problem please type where cmd in a normal command window then show the output here?

arjunkharbanda commented 8 years ago

capture here you go

tomlau10 commented 8 years ago

output seems normal... how about where cmd at your source files' path ?

does only that source file will invoke the StartDB.bat or other source files at different paths also have the same issue?

tomlau10 commented 8 years ago

ahh... in your first figure the Start Database Properties, press the general tab and see where is the location of that shortcut?

i think maybe deleting that shortcut will help (click Shortcut tab and press Open file location will take you there) back it up first though :sweat_smile:

arjunkharbanda commented 8 years ago

screenshot 10 So I uninstall Oracle DatabaseXE and this is what this is what happen looks like problem solved but here is catch capture The target is still sysWOW64 C:/Windows/SysWOW64/ to be more accurate and I have to reinstall Oracle Database XE as I am student and it is part of my course so I guess I have to use it like this even if I don't like this lastly I want to help you in this please let me know how to start with JSON/CSON and also do you want me to close this issue

tomlau10 commented 8 years ago

For a 64bit windows, sysWOW64 actually means the 32bit version and system32 means the 64bit version, see this link

so C:\Windows\SysWOW64\cmd.exe is the 32 bit version cmd and i don't think it will cause problem when executing the built executable. i also realized in my case, the plugin also invokes the sysWOW64 cmd. Does it cause problems when using anyway in your case?

for learning, I strongly recommend starting with Learn X in Y minutes This is an excellent site providing a good start for many languages and it contains further readings as well

I think this issue is not related to the usage or bug in this plugin so I will close it for now. Be sure to open new issue if you have new problems :smile: