Recent Posts

Pages: 1 [2] 3 4 5 6 7 ... 10
11
Help / Re: Strange Syntax Error Using MIPS Compiler
« Last post by Authentic on Yesterday at 07:57:28 pm »
Thank you for responding! I am going to start rebuilding the compiler now to see if that works. Here is the build log:

Code: [Select]
Build started on: 20-10-2017 at 12:53.57
Build ended on: 20-10-2017 at 12:53.57
-------------- Build: Debug in test (compiler: n64)---------------
mips64-g++.exe -o bin\Debug\test.exe obj\Debug\test.o -T "C:\Program Files (x86)\CodeBlocks\n64-master"/ldscripts/gl-n64.ld -Wl,--defsym,start=0x -specs=nosys.specs -flto -Wl,--gc-sections
c:/msys64/opt/n64-toolchain/bin/../lib/gcc/mips64/7.2.0/../../../../mips64/bin/ld.exe:--defsym:1: syntax error
collect2.exe: error: ld returned 1 exit status
Process terminated with status 1 (0 minute(s), 0 second(s))
2 error(s), 0 warning(s) (0 minute(s), 0 second(s))
12
Development / Re: Compiler generated files bug?
« Last post by oBFusCATed on Yesterday at 07:53:14 pm »
Does it work if you do the replacements before the c-tor of wxfilename?
13
Help / Re: Project parser completes, nohing displayed in "symbols" window
« Last post by ravenspoint on Yesterday at 05:13:55 pm »
The "one parser per workspace" option looks interesting.

It was a little hard to find - Settings | Editor | Code completion | C/C++ Parser

but once found and selected, I can see my symbols again!
14
Development / Compiler generated files bug?
« Last post by BlueHazzard on Yesterday at 01:39:08 pm »
I want to use protobuf and use advanced compiler options for this.
I use
Code: [Select]
protoc -I$file_dir --cpp_out=proto $filefor the compiler command. So all source files will be created in the "proto" sub folder of the project
and i use this for the autogenerated files:
Code: [Select]
proto/$file_name.pb.cc
proto/$file_name.pb.h
But this does not work.
It searches the file in the base path of the project. So ignores the "proto" part of the directory....

i looked into the code and this is quite specious:
Code: [Select]
         wxFileName tmp
...
tmp.SetFullName(tool->generatedFiles[i]);
                wxString tmps = tmp.GetFullPath();
                // any macro replacements here, should also be done in
                // CompilerCommandGenerator::GenerateCommandLine !!!
                tmps.Replace(_T("$file_basename"), pf->file.GetName()); // old way - remove later
                tmps.Replace(_T("$file_name"),     pf->file.GetName());
                tmps.Replace(_T("$file_dir"),      pf->file.GetPath());
                tmps.Replace(_T("$file_ext"),      pf->file.GetExt());
                tmps.Replace(_T("$file"),          pf->file.GetFullName());
                Manager::Get()->GetMacrosManager()->ReplaceMacros(tmps);

                ProjectFile* pfile = AddFile(targetIndex, UnixFilename(tmps));

is it a good idea to give wxFileName a string that cans contain "$" charachters? Why not replace the path before passing it to a wxFileName object?
15
Help / Re: Strange Syntax Error Using MIPS Compiler
« Last post by stahta01 on Yesterday at 01:27:07 pm »
While waiting for the downloads to finish, I am guessing n64.conf is not correct and needs edited to fix this error.

NOTE: It looks like this git project expects an CB "Custom makefile" project instead of a normal CB project like you are trying to use.

But, till you post the requested full build log I will not know what you are trying to use for certain.

Tim S. 
16
Help / Re: Strange Syntax Error Using MIPS Compiler
« Last post by stahta01 on Yesterday at 12:43:04 pm »
Post a full rebuild log of your simple program and post the simple program.
http://wiki.codeblocks.org/index.php/FAQ-Compiling_(errors)#Q:_How_do_I_troubleshoot_a_compiler_problem.3F

I am trying to build the n64 compiler, right now. But, I have a slow internet connection and a slow computer.

Likely something changed in the Compiler or Code::Blocks (CB) that requires the CB settings to be changed.

Tim S.
17
Help / Strange Syntax Error Using MIPS Compiler
« Last post by Authentic on Yesterday at 12:16:31 pm »
Recently I installed Code::Blocks and everything worked with the mingw compiler. But after following this guide (to the letter) I find myself unable to build even the simplest valid C programs: https://github.com/glankk/n64. The error is always the same:

Code: [Select]
||=== Build: Debug in test (compiler: n64) ===|
c:\msys64\opt\n64-toolchain\bin\..\lib\gcc\mips64\7.2.0\..\..\..\..\mips64\bin\ld.exe:--defsym|1|syntax error|
||error: ld returned 1 exit status|
||=== Build failed: 2 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|

I am using Code::Blocks 16.01, and here is an example of a c file that won't build:

Code: [Select]
int main() {
    return 0;
}

I don't want to waste anyone's time if this is a simple problem, but I really cannot find a solution. Do I need to rebuild the compiler?
18
Nightly builds / Re: The 19 October 2017 build (11210) is out.
« Last post by Melchior on Yesterday at 11:50:32 am »
Quote
'Save All', 'Save all projects'
Are the same as "Save everything"

Quote
'Close all project'
Same as "Close workspace"
lol ooh  oook.... ;)
19
Nightly builds / Re: The 19 October 2017 build (11210) is out.
« Last post by BlueHazzard on Yesterday at 11:48:21 am »
Quote
'Save All', 'Save all projects'
Are the same as "Save everything". Where is the difference between "Save all" and "Save all projects"?

Quote
'Close all project'
Same as "Close workspace"
20
Nightly builds / Re: The 19 October 2017 build (11210) is out.
« Last post by Melchior on Yesterday at 11:35:28 am »
ok.. BUT

"UI: Remove 'Save All', 'Save all projects' and 'Close all project' menu items from the File menu"

This sucks... why remove it?! :/
Pages: 1 [2] 3 4 5 6 7 ... 10