Menu
▾
▴
#1115 FortranProject still referenced in truck workspaces and Makefile.am & update.bat
At some stage in the past the src\plugins\contrib\FortranProject has been removed from the tucnk and setup as a separate project on SF, but there are still references to it in the following files:
src\CodeBlocks_wx31.workspace
src\CodeBlocks_wx31_64.workspace
src\ContribPlugins_wx30-unix.workspace
src\ContribPlugins_wx31.workspace
src\ContribPlugins_wx31_64.workspace
src\plugins\contrib\Makefile.am
src\update.bat
When loading a workspace you get the following error in the log and a pop up indicating "1 projects could not be loaded" occurs:
Unable to open "plugins\contrib\FortranProject\FortranProject_cbsvn_wx31_64.cbp" during opening workspace "F:\Andrew_Development\CB_AutoDetectCompilerStartup\src\CodeBlocks_wx31_64.workspace"
The same pop up occurs when build on windows via the batch files, which requires the devleoper to click on OK to continue with the build.
Use svn and it will work.
It seems to be a bit more complex than that just saying use SVN because:
1) Looks like it's been setup as an external in SVN.
2) When using SF's HTTP access to the trunk the directory does not show up.
3) The fortran plugin is run as a separate project on SF. This is probably why 1) above is configured like it is and makes sense.
So the real problem is that anyone using any of the github repo's are NOT getting the full source as far as I can see, but this disclaimer or info regarding this is not included anywhere in the wiki or forums that I have seen.
As such this may be technically invalid if using SVN, but as allot of devs have moved on from SVN and now use Git and as such when using the git link on the following wiki page or the links in the forums will fall into the same hole as I have and probably the same assumptions as to what has gone wrong as indicated in the first paragraph:
https://wiki.codeblocks.org/index.php/Developer_documentation