User forums > General (but related to Code::Blocks)
Projectfiles on other drives
mandrav:
--- Quote from: MadMeX ---Can I include the file with an absolute path ?
--- End quote ---
--- Quote from: MadMeX ---<Unit filename="$(#jennicsdk)\Chip\Common\Source\Printf.c">
--- End quote ---
The moment you start describing your problems accurately, we may be in a position to help you...
MadMeX:
--- Quote from: mandrav on December 01, 2007, 10:44:18 pm ---
--- Quote from: MadMeX ---Can I include the file with an absolute path ?
--- End quote ---
--- Quote from: MadMeX ---<Unit filename="$(#jennicsdk)\Chip\Common\Source\Printf.c">
--- End quote ---
The moment you start describing your problems accurately, we may be in a position to help you...
--- End quote ---
Ok, in my first post i did not understand the problem. please remember for a moment only the last post. There I described my actual problem.
As far as I understand my problem, C:B generates a path for the .o relative to the .objs similiar to the location on the drive. And because of windows filenames a directory name of c: isn't allowed, so it generates .objsC. So there is some kind of reinterpretation of c:\... to objsC\... But when the unit-filename is composed of a variable, this reinterpretation is not done, when gernerating the full filename for the ba-elf-ld linker - see the errormessage, it should be ..\JN5139_Build\Debug\.objsC\.... passed to ld, but then the file would be found.
so my question is: is this a bug or am i using the compiler-var the wrong way? I want to include a file relative to a compiler-var, like the first <unit filename>-block, so that it is an absolute path like the second block (which should be the same, as far as I understand)
I hope this is now clearer. (my first description with an absolute path was wrong, because i not realised the structured objs... dirs)
Thanks
MeX
stahta01:
I am taking the time to try to understand your issue.
I am downloading JN-SW-4026-SDKwithIDE-1v5.0.msi to try to duplicate your setup.
Do you know what complier is being used?
I saw the word CygWin in the path and I am guessing a custom version of CygWin GCC, is this correct?
If it is CygWin, that may be the issue, it is not tested very often so it might have bugs in the current version.
File, 90 MB, being downloaded from here. It going real slow, might be a while to finish.
http://www.jennic.com/files/support_files/JN-SW-4026-SDKwithIDE-1v5.0.msi
--- Quote ---development kit on drive c:\ and my project reside on a network share, say z:\
--- End quote ---
Is the following correct?
jennicSDK is on drive C: (Local Drive)
Project source code is on drive Z: (Network Drive)
Project cbp file is on drive Z: (Network Drive)
Which drive is the compiler on?
Which sample application code::blocks project file is closest to yours?
I need one to try to compile, I may need to ask you questions about some basic things; since, I have no knowledge of this stuff. But, I know Code::Blocks and I have some time till tomorrow when I may need to go to College.
The problem seems to be they assume the SDK and the project using it are on the same drive. I will have to change the sample app into two projects each.
Note, I don't have an Network Drive, so can only test it on a different drive letter.
Tim S
stahta01:
I have uploaded two code::Blocks files to
http://www.savefile.com/projects/1039215
File is called jennicCBP.7z
I used $(#jennicsdk)=C:\Jennic\cygwin\jennic\SDK
Place the project jennicSDK.cbp into the folder C:\Jennic\cygwin\jennic\SDK it must be compiled first.
It creates a static library called mySDK that is used by your project file.
The second project is JN5139R1_Coordinator.cbp which I used as the example user project.
I tested it with SVN 3466 and 4717.
Tim S
For my Future Info:
The compiler name is jn51xx_compiler used CygWin as compiler to copy.
Compiler program settings are
Folder C:\Jennic\cygwin\ba-elf
ba-elf-gcc.exe
ba-elf-g++.exe
ba-elf-ld.exe
ba-elf-ar.exe
ba-elf-gdb.exe
Note: Linker did not like to use linker search directories to find the libraries; I had to place the relative or full path in the library name entry area.
MadMeX:
Great THANKS for your help !!
and spending your time !
It works fine. :)
There is only one little problem left. If I compile the static-lib, ranlib shall be called, but there is no ranlib. My workaround is to rename the ba-elf-ranlib to ranlib, but how can I tell C:B, what name "ranlib" has ? I didn't found the field in the compiler-settings.
Thanks
MeX
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version