Oh, this is why; the activation logic has changed.
Index: src/plugins/contrib/SmartIndent/CppSmartIndent.cpp
===================================================================
--- src/plugins/contrib/SmartIndent/CppSmartIndent.cpp (revision 8428)
+++ src/plugins/contrib/SmartIndent/CppSmartIndent.cpp (working copy)
@@ -74,7 +74,7 @@
const wxChar ch = event.GetKey();
- if ( SelectionBraceCompletionEnabled() )
+ if ( SelectionBraceCompletionEnabled() || stc->IsBraceShortcutActive() ) // the shortcut is Alt-I
DoSelectionBraceCompletion(stc, ch);
DoSmartIndent(ed, ch);
@@ -464,7 +464,7 @@
void CppSmartIndent::DoSelectionBraceCompletion(cbStyledTextCtrl* control, const wxChar &ch)const
{
- if (( control->IsBraceShortcutActive()) && !control->GetLastSelectedText().IsEmpty())
+ if (!control->GetLastSelectedText().IsEmpty())
{
const int pos = control->GetCurrentPos();
Invalid manifest file for: LuaSmartIndent
Invalid manifest file for: CppSmartIndent
Anyone seeing this in the log? And both Lua and Cpp plugins are not loaded, nor are visible in the Plugins->Manage... dialog.
This is on linux using the autotools build system, rev 8500, but I'm seeing this for a while now.
p.s. can someone rename the plugins to SmartIndentXXX instead of XXXSmartIndent
today : svn up + make clean + make + sudo make install
It even got worse :
Tools Plus Plugin: Registering shell type Piped Process Control
Plugin manifest could not be parsed: /usr/local/share/codeblocks/FortranSmartIndent.zip
Plugin manifest could not be parsed: /usr/local/share/codeblocks/SmartIndentCpp.zip
Invalid manifest file for: HDLSmartIndent
Invalid manifest file for: SmartIndentXML
Invalid manifest file for: PascalSmartIndent
Plugin manifest could not be parsed: /usr/local/share/codeblocks/SmartIndentHDL.zip
Plugin manifest could not be parsed: /usr/local/share/codeblocks/SmartIndentPython.zip
Invalid manifest file for: LuaSmartIndent
Invalid manifest file for: PythonSmartIndent
Plugin manifest could not be parsed: /usr/local/share/codeblocks/SmartIndentPascal.zip
okay, so I did :
- make distclean
- ./bootstrap
- ./configure --with-contrib-plugins=all
- make -j12
- sudo make install
==> does not make any difference
Loaded 0 plugins
Scanning for plugins in /usr/local/lib64/codeblocks/plugins
Tools Plus Plugin: Registering shell type Piped Process Control
Plugin manifest could not be parsed: /usr/local/share/codeblocks/FortranSmartIndent.zip
Invalid manifest file for: SmartIndentCpp
Invalid manifest file for: HDLSmartIndent
Invalid manifest file for: PascalSmartIndent
Plugin manifest could not be parsed: /usr/local/share/codeblocks/SmartIndentHDL.zip
Invalid manifest file for: SmartIndentPython
Invalid manifest file for: LuaSmartIndent
Invalid manifest file for: PythonSmartIndent
Plugin manifest could not be parsed: /usr/local/share/codeblocks/SmartIndentPascal.zip
Invalid manifest file for: SmartIndentFortran
Loaded 59 plugins
Darn autof*** :-(
while I had "/usr/local/lib64/codeblocks/plugins/" open in dolphin,
I did ==> sudo make uninstall
==> all disappeared except :
-rwxr-xr-x 1 root root 1613 Nov 5 07:31 libCppSmartIndent.la
-rwxr-xr-x 1 root root 63650 Nov 5 07:31 libCppSmartIndent.so
-rwxr-xr-x 1 root root 1637 Nov 5 07:31 libFortranSmartIndent.la
-rwxr-xr-x 1 root root 38766 Nov 5 07:31 libFortranSmartIndent.so
-rwxr-xr-x 1 root root 1613 Nov 5 07:31 libHDLSmartIndent.la
-rwxr-xr-x 1 root root 47849 Nov 5 07:31 libHDLSmartIndent.so
-rwxr-xr-x 1 root root 1613 Nov 5 07:31 libLuaSmartIndent.la
-rwxr-xr-x 1 root root 38317 Nov 5 07:31 libLuaSmartIndent.so
-rwxr-xr-x 1 root root 1631 Nov 5 07:31 libPascalSmartIndent.la
-rwxr-xr-x 1 root root 39042 Nov 5 07:31 libPascalSmartIndent.so
-rwxr-xr-x 1 root root 1631 Nov 5 07:31 libPythonSmartIndent.la
-rwxr-xr-x 1 root root 38167 Nov 5 07:31 libPythonSmartIndent.so
-rwxr-xr-x 1 root root 1613 Nov 5 07:31 libXMLSmartIndent.la
-rwxr-xr-x 1 root root 43792 Nov 5 07:31 libXMLSmartIndent.so
I think there's something seriously wrong with out build scripts / makefiles
EDIT : new approach starting with
- rm -rf * in trunk and svn up
- usr/local/share/codeblocks ==> manualy deleted
- usr/local/include/codeblocks ==> manualy deleted
- usr/local/lib64/codeblocks ==> manualy deleted
and then the entire chain again ......... [will paste the result .....]
FAILURE :
zip -R /home/killerbot/CodeBlocks/trunk/src/plugins/contrib/SmartIndent/SmartIndentPython.zip manifest.xml
PWD=`pwd` cd . && \
cp manifest_lua.xml ./manifest.xml && \
zip -R /home/killerbot/CodeBlocks/trunk/src/plugins/contrib/SmartIndent/SmartIndentLua.zip manifest.xml
cp: cannot create regular file `./manifest.xml': File exists
adding: manifest.xml (deflated 50%)
adding: manifest.xmlmake[4]: *** [SmartIndentHDL.zip] Error 1
zip warning: file size changed while zipping manifest.xml
adding: manifest.xml (stored 0%)
(deflated 50%)
damn damn damn
EDIT :
issued again : make -j12 ==> continues till the end
then issued : sudo make install : OK
and then we run it and we get (to be honest as expected :-( ) :
Loaded 0 plugins
Scanning for plugins in /usr/local/lib64/codeblocks/plugins
Tools Plus Plugin: Registering shell type Piped Process Control
Invalid manifest file for: SmartIndentCpp
Invalid manifest file for: SmartIndentHDL
Invalid manifest file for: SmartIndentPython
Invalid manifest file for: SmartIndentPascal
Loaded 55 plugins
There's something wrong with those SmartIndent, and it seems also not save to touch that area with a make -j12 ??
Never had any build problems before, but it seems SmartIndent is causing problems ...
1. Why don't you use packages? Provided by Jens or self build
2. Why don't you use prefix (--prefix=/home/myname/software/codeblocks for example), make uninstall is known to be unreliable, especially when there are changes to the filenames
3. For cleaner builds you can use something like:
./bootstrap
cd build
rm -rf *
`pwd`/../configure
make -jn
make install
Most of the time I stick to 1 and I'm happy...
This time I suspect there is some misery happening in the Makefiles, which is not 100% reliable.
What happens if you use make -j1?
I will look into it as soon as possible.
A very easy solution would be to move the manifest into sub-folders "HDL", "Cpp".... Then you don't need to rename and can run the ZIP commands in parallel w/o hassle.
@killerbot:
can you test the following patch, please:
Index: src/plugins/contrib/SmartIndent/Makefile.am
===================================================================
--- src/plugins/contrib/SmartIndent/Makefile.am
+++ src/plugins/contrib/SmartIndent/Makefile.am
@@ -99,6 +99,8 @@
CLEANFILES = $(pkgdata_DATA)
+.NOTPARALLEL: $(pkgdata_DATA)
+
SmartIndentHDL.zip: manifest_hdl.xml
PWD=`pwd` cd $(srcdir) && \
cp manifest_hdl.xml ./manifest.xml && \
I can build with it, but there haven't been any issues before (with -j 2).
I tested with -j 4, but I have just a core2duo, so I might not have enough cores to break the build.