News Alert
|
B.C. sex tourist sentenced to 11 years Kenneth Klassen of Burnaby, B.C., convicted of child sex tourism and importing child pornography, has been sentenced to 11 years in prison. |
Newest legal info, hacks, tricks and tips of web development, iSO and Andriod and specialist of SEO.
|
B.C. sex tourist sentenced to 11 years Kenneth Klassen of Burnaby, B.C., convicted of child sex tourism and importing child pornography, has been sentenced to 11 years in prison. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
cd build/src680-m66 . ./LinuxX86Env.Set.sh cd vclNow have a hack at vcl/source/window/menu.cxx (Menu::SetItemText); (near line 1770) I suggest manually applying this change:
- pData->aText = rStr; + pData->aText = String(rStr).Reverse();Then save. ( You can find more sensible things to hack in the Tutorials )
soffice -writer. You should notice the effect in the menus.
If not, ensure the previous soffice.bin was dead with
killall -9 soffice.bin
[action]: [arguments]
mkdir: %_DEST%\inc%_EXT%\external
where if '[action]:' is omitted, it defaults to the 'copy' action. Typical actions are copy, mkdir, touch, hedabu, dos and linklib.
During the action, various macro variables are expanded some of which are:
..\%__SRC%\inc\sal\*.h %_DEST%\inc%_EXT%\sal\*.hNB. relative paths are relative to the 'prj/' directory.
char *, please? rtl_String — sal/inc/rtl/string.hrtlstring->buffer is useful, as is
rtlstring->length. This object encapsulates
an generic 8bit string - of unknown encoding. Feel free to treat
rtlstring->buffer as your beloved char *.
If you really want to look at the implementation of some
rtl_String function and lxr nor grep can help you, have
a look at sal/rtl/source/strtmpl.c.
OString — sal/inc/rtl/string.hxxclass; you
can use ostring.pData to get at the rtl_String
(it's public). OString has reasonably useful
methods for if you need them.
rtl_uString — sal/inc/rtl/ustring.hrtl_String above to find where the implementation
of some rtl_uStringfunctions is hidden.
OUString — sal/inc/rtl/ustring.hxxclass. This is
what most of the OO.o code uses to pass strings around.
To convert an OString to an OUString
it is necessary to specify the character set of the
OString see; sal/inc/rtl/textenc.h
— the only interesting case is RTL_TEXTENCODING_UTF8
String — tools/inc/string.hxxGetBuffer(), but it's Utf-16 encoded.
rtl::OString aOString = ::rtl::OUStringToOString (aOUString, RTL_TEXTENCODING_UTF8);
rtl::OUString aOUString = ::rtl::OStringToOUString (aOString, RTL_TEXTENCODING_UTF8);
#define CHAR_POINTER(THE_OUSTRING) ::rtl::OUStringToOString (THE_OUSTRING, RTL_TEXTENCODING_UTF8).pData->buffer
printf ( "SvXMLNamespaceMap::AddIfKnown : %s / %s\n", CHAR_POINTER(rPrefix), CHAR_POINTER(rName) );.
printf ( "rGrfName : %s\n", ByteString( rGrfName, RTL_TEXTENCODING_UTF8).GetBuffer() );
dbg_dump().
It is intended to be called interactively from the debugger, in both
debug and non-debug builds of OOo. You can see the definition in
sal/rtl/source/debugprint.cxx.
-l
functionality of bin/ooinstall. It essentially
sym-links files of similar names into your local tree,
allowing a fast development iteration.
cppuhelper and configmgr,
thus in the rare case that these are altered, they
must be copied manually into /opt/OOInstall/program.
desktop/unxlngi4.pro/bin/soffice NB. with an appended '.bin'
cd binfilter
cat CVS/Repository
framework/binfilter
This shows you that the 'binfilter' directory is part of the 'framework' project.
-writer, -calc, -draw,
and (the wizardly painful) -impress arguments.
vc vcl : NAS:nas FREETYPE:freetype psprint rsc sot ucbhelper unotools sysui NULL
vc vcl usr1 - all vc_mkout NULL
vc vcl\source\unotypes nmake - all vc_unot NULL
vc vcl\source\glyphs nmake - all vc_glyphs vc_unot NULL
...
vc vcl\mac\source\src nmake - m vc__srcm vc_unot NULL
vc vcl\util nmake - all
vc_util vc__plug.u vc__appa.u vc__appm.m vc__appu.u vc__appw.w vc__gdim.m
vc__gdiu.u vc__gdiw.w vc__srcm.m vc__srcu.u vc__srcw.w
vc__wina.u vc__winm.m vc__winu.u vc__winw.w vc__du.u
vc__gtka.u vc__gtkw.u vc__gtkg.u vc__kde.u vc_app
vc_ctrl vc_gdi vc_hlp vc_src vc_win vc_glyphs NULL
so we need to try and un-pack what's going on here, which is in fact
not
as odd as it might seem at first glance. Firstly lists are terminated
by the 'NULL' string. Every line is prefixed by a shortcut which has to
be unique, no two modules are allowed to have the same shortcut.
[shortcut] [path to dir to build] nmake - [flags] [unique-name] [deps...] NULL
vc vcl\source\glyphs nmake - all vc_glyphs vc_unot NULL
shortcut is not used; flags determines which platforms
this builds on; usually single char platform codes: 'dnpum' 'u' being
Unix. The higher up the system, the more stuff is flagged 'all'.