I see now that we have rev 3002, but the command "port upgrade devel/codeblocks" is not detecting any changes, and updates nothing.
Is there a way to get darwinports( or MacPorts as it is called nowadays) to upgrade codeblocks?
Manual build also works for me, but I have not yet been able to create a working CodeBlocks.app bundle "manually" using the wiki instructions. I would need to get some VERY detailed instructions on how to create a working CodeBlocks bundle from a "svn update", ./bootstrap, ./configue and make. This would help me to be updated.
The darwinport version is using symlinks from the bundle to the installation in /opt/local.
In my manual build, I use --prefix=$HOME not to interfere. In my bunding attempt I try to use symlinks to ~/bin/codeblocks etc., otherwise I try to follow the wiki instructions. The problem is that CB does not find the plugins.
The current darwinport installation prescribes some patches, which are available on the wiki page. As the project develops, I assume that these patches may or may not be applicable since they may already be implemented. There may also be new patches required. How do you handle this?
The wiki instructions on how to make a bundle is very different from how your darwinport is doing it.
The method described in the wiki is moving the complete installation hierarchy into the bundle, while your port is making symliks to the installation in /opt/local. You may want to comment on this.
The wiki bundle description is not perfectly clear as I see it.
For instance, why is the last three lines in the hierarchy list written in italic?
Under "Proper bundling" you write that codeblocks and the dynamic libraries should be moved to MacOS from bin and lib.
What about "cb_console_runner"?
And should everything in lib be moved or only "libcodeblocks.0.0.1.dylib".
Is "libcodeblocks.la" also a dynamic library?
I think I get the most of the story, except the very last "post-install".
Could you describe exacltly what steps are required to make a manual symlink bundle work?
This is mainly for two reasons:
1) It is quicker for me to "update by make" since darwinports update would require a full rebuild;
2) I have a chance to participate in the debug process (not very likely, but anyway) since I have access to source code and make output. I am hesitant to mess around with the /opt/local, I have had serious port problems before when I did this;
How does CB decide where to look for the resources?
The "wiki bundle" looks for it in Contents/share/codeblocks, while the "symlink bundle" looks in Contents/Resources. Still the source code is the same?
/usr/bin/cb_console_runner
/usr/share/man/man1/cb_console_runner.1