|
Post by dshadoff on Jan 19, 2020 2:09:39 GMT
My first guess would be that it's naming-related (for example, spaces in the name or something). Next guess would be path/name too long... I don't think it would be locale-related per se, but certain characters used in that locale might be illegal (also not sure about unicode usage...)
|
|
|
Post by elmer on Jan 19, 2020 2:28:32 GMT
My first guess would be that it's naming-related (for example, spaces in the name or something). Next guess would be path/name too long... I don't think it would be locale-related per se, but certain characters used in that locale might be illegal (also not sure about unicode usage...) Yes, it actually has turned out to be a very interesting problem! The most-recent build of HuC that I added a few messages ago is totally fine with spaces in paths or the filename itself, so that shouldn't be the problem. I'm really curious to see what is going wrong. Anyway, makaimura , here is another build script to try that will give us more information about what is going wrong. huc_debug.cmd (1.74 KB) Please put it in your huc/bin/ directory, and then drag-n-drop your .c file onto it. When it finishes (either OK, or with an error), it will pause and leave the command window open. If you click on the little icon on the top-left of the window, it should bring up a menu. Select "Edit" and then "Select All", which should highlight everything in the window. Then press the "Enter" to copy all of the window contents to your clipboard. Please send us message with that information. You should just have to press "Reply" on this thread, and then press "Ctrl-V" on your keyboard to copy everything into the message (or right-click and select "Paste" on the menu).
|
|
|
Post by Arkhan on Jan 20, 2020 4:13:15 GMT
I seem to recall on japanese systems, there were issues with slashes being treated as the ¥ symbol, and it threw things for a loop.
|
|
|
Post by makaimura on Jan 21, 2020 3:32:45 GMT
Hi Guys ! elmer : I have done the thing you asked me to do. Here are the pictures. CMD windows appears and disappears quick. Some times they stay most of the time they appear and disappear in a flash. Anyway, Still no luck. I used 2 build. A old one and the latest you gave me. Reading the result it seem that the program cannot find HUC.exe.... @_@....is that the problem? Also I have included the hello.c file. About this, I would be surprised if a problem is from there. Created in notepad, saved as .c. Attachments:
Hello.c (340 B)
|
|
|
Post by elmer on Jan 21, 2020 4:02:36 GMT
Also I have included the hello.c file. About this, I would be surprised if a problem is from there. Created in notepad, saved as .c. Thanks! OK, I'm not sure why the build script is saying that it can't find "huc.exe", that's a bug on my part that I will have to look for. Apart from that, "yes", there is a serious problem with the "hello.c" file that you have uploaded ... it has been saved in Unicode text format, and HuC just can't deal with that. I don't know if that is a problem with the upload, or if the problem exists in the file on your computer. When you open the file in Notepad++, there should be a status bar at the bottom of the window. When I open your hello.c file, the 2nd-to-last thing on that status bar says "UCS-2 LE BOM", which indicates that the file is in Unicode format. If you go to the "Encoding" menu at the top of the Window, please change the format to "Encode in ANSI" and save the file again, then that message on the status bar should say "ANSI". If you do that and try to compile the file again, do you get any different results?
|
|
|
Post by makaimura on Jan 21, 2020 13:16:46 GMT
Thank you!!! Well....... everyone start learning as a noob , I am learning . Indeed it was the Hello.c file. The bloody encoding. I will never forget this one . Sorry for the headache LOL! Now I am set to continue the tutorial. I am going to experiment. I realize , learning coding is difficult. I hope from now all my problems will be in the assembly lines and not on how to use the tools. I will be much more attentive from now on! elmer Arkhan and all you guys Thank you very much!! Attachments:
|
|
|
Post by turboxray on Jan 21, 2020 19:51:30 GMT
Thank you!!! Well....... everyone start learning as a noob , I am learning . Indeed it was the Hello.c file. The bloody encoding. I will never forget this one . Sorry for the headache LOL! Now I am set to continue the tutorial. I am going to experiment. I realize , learning coding is difficult. I hope from now all my problems will be in the assembly lines and not on how to use the tools. I will be much more attentive from now on! elmer Arkhan and all you guys Thank you very much!! I had issue once with text encoding. I had a spec that specifically said ascii only text files (I even verified that there would only be ascii text files). And I was making something cross platform (windows and linux). Somehow in a test, someone had a couple bytes of unicode at the start of a text file (we were parsing it for config info), and the windows library ignored it and only passed in ascii.. linux library did not! And bad things happened haha. I never forgot that!
|
|
|
Post by makaimura on Jan 23, 2020 3:21:49 GMT
turboxray Yeah! I understand the troubles you had. Thanks that I have not done what I was planning to do lolz.... I was on the way to cross platform between Xubuntu on a laptop and win 8.1 pad. Pad for creating my pixels and coding to xubuntu for compiling since huc was giving me troubles. It would have be a god damn Greek tragedy. Elmer would have lost is marbles on that one lol When starting the tutorial, the tutorial mentioned specifically to " Create a new file and save it as hello.c. Make sure this file is saved as plain text... as much as some word processors make some very pretty text, the compiler won't be able to understand the special formatting that they use so make sure you do not format the text in any way. That means no colors, no font changes, no bold, no justify, no tables, or any of that kind of fancy stuff... just good old text." Having did that I was confident it will be the least of my troubles. Then frustrated I installed a text editor more... codemaker like . I saw the "encoding" option but did not ring any bells since I saved my file as .c (thinking that it is the basic for .c to be readable for what I am doing right now.) ANSI....... ok lol . Bad experiences forge the skills. Negative turn into positive learning with the right people
|
|