Suppose you want to statically link some libraries and some others dynamically when building your executable with the GCC/G++ toolchain. For sure you can pass the static library with its full path along with the other objects, something like:
gcc -o executable anObject.o /usr/lib/someLibrary.a
But what if I don't want to search library full path? What if I want to use standard library search path? In short: how the hell do I tell the linker to manage this stuff?
Here are the relevant options:
WARNING: linking order in the static chain matters!
An example:
gcc -o executable anObject.o -Wl,-Bstatic -lstaticLib -Wl,-Bdynamic -ldl -lpthread -ldynamicLib
libstaticLib.a will be used, even if a libstaticLib.so is available.
IMAPfilter is used to check if there are already read messages in the mailbox, mutt does the download and save job.
Here's how to wrap up the stuff: substitute values to suit your needs
READMSG=$(imapfilter -e "account=IMAP{server = 'mail.somedomain.com',username = 'someuser',password = 'somepasswd'} \
exist, unread, unseen = account.INBOX:check_status() \
print (exist - unseen)" | grep -v messages)
echo "Mailsize - someuser: $READMSG"
if [[ $READMSG -gt 0 ]]; then
mutt -e "push ~R=someuser-$(date +"%b-%Y").gz" \
-f 'imap://someuser:somepasswd@mail.somedomain.com' >/dev/null
fi
Commands should be on a single line, so join the lines split by a '\' Cannot open self ./myProg or archive ./myProg.pkgThis is all because of executable stripping. By default EPM strips executables, and frozen python exes don't work anymore. So, in your EPM list file, remember to use the nostrip() directive, like here:
f 755 user group ${prefix}/myProg ${srcdir}/myProg nostrip()
If you want to deploy stripped executables, use strip=True as arguments in your EXE and COLLECT objects in the PyInstaller spec file.
Fuck code signing/security/whatsoever: let MY hardware execute what I want, huh?
I read somewhere that this can be done using Visual Studio 2008; don't know, as I don't (still) use the beast.Device Command Shell (DCS) provides a command-line interface to several useful functions for developing Smart Device applications using Visual Studio 2005. It is implemented as a Visual Studio "Command Window" add-in for convenience and quick access.This is the author description for DCS. Useful tools, indeed. Download URL used to be http://www.gotdotnet.com/workspaces/workspace.aspx?id=50618f79-c7b1-4588-9c0a-cf4ddae8092a but seems that M$ is moving everything to MSDN Code Gallery and this stuff got lost somewhere. OK, don't know if it's OK for me to redistribute, but many seem to need this...
Download Device Command Shell here: DeviceCommandShellSetup.zip
But at long last I was able to put all the pieces together:
Server failed to listen on 192.168.0.103Standard useless error message. Ok, there must be this old address configured somewhere. In the registry, of course. Just searched throughout the whole registry and found:1433. Error: 0x2741. To proceed, notify your system administrator.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\TcpHere you'll find subkeys named IP1 to IPSomeNumber. If one refers to an unbindable address just set Enabled or Active to 0.
| 2X PM10244-70 T9210 1X M5M41000BJ 234GE20-7 |
1 MB |
| 1X TMS4C1024DJ HEP 3312 24 2X TMS44400DJ OBI 4051 AH |
1 MB |
| 2X KOREA AO169315GGG HM514400AS7 1X KOREA A0029305GGGK HM511000AJP7 |
1 MB |
|
|
February '10 | |||||
| Mo | Tu | We | Th | Fr | Sa | Su |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 16 | 17 | 18 | 19 | 20 | 21 |
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
2006-2008 Giuseppe 'Cowo' Corbelli | Cowo's homepage | Cowo's photo page | Contact me | Back to top
Design by Andreas Viklund | Serendipity Template by Carl