Saturday, March 31, 2007
WinCE -- How to speed up build process
1. say any project change u could build selected project and then makeimg.
make sure ur WINCEREL=1
2. use command prompt.
set WINCEREL=1---> to make sure that whatever u build is copied to release
directory.
go to the target directory and run build -c
and then do makeimg
for platform.bib etc files..just do the changes and copy paste in ur release
directory. and then run makeimage..this will save enough time.
The batch file "blddemo" does a lot of things to build a final image. It
also has a number of shortcuts to speed things up.
Simplified overview of what blddemo does
* SYSGEN Phase
This phase builds the CE kernel based on your selected SYSGEN variables and
BSP variables
- Build anything in Private if needed
- Build everything in Public
- Build your BSP under the Platform directory
* Buildrel Phase
- Copies your built files to the _FLATRELEASEDIR
* Makeimg Phase
- Creates the final NK.BIN based on stuff in the _FLATRELEASEDIR and your
IMG flags
*** Tricks to Speed things up ***
blddemo -q
This will skip building the Private directory. Normally, you never
change anything here anyway so you are just wasting time calculating
dependecies.
blddemo -qbsp
This is new in 5.0 and skips both Private and Public and only builds
your BSP platform. This is common when you are developing device drivers
for a BSP and didn't change the features you bring into your OS Design (no
SYSGEN or BSP variable changes)
WINCEREL=1
When you are building something in PUBLIC and then run makeimg, you
won't see the DLL in you Flat Release DIr (FRD) because it wasn't copied
there. The build system only does that in the buildrel phase which you
skipped. By setting WINCEREL=1 you get the DLL copied to the FRD as the
last step
Targeted Builds (5.0 using the IDE for your builds)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wceo...
tml/wce50tskrunningtargetedbuild.asp
Skipping makeimg by using Release Directory Modules list
If you are debugging an image already flashed to the device, you can
tell the CE filesystem loader to grab your DLL from your PC (in the FRD)
rather than use the one built inside the NK.BIN. This means you can skip
the makeimg step if your newly-built DLL is in the FRD. To do this, go to
the Menu Target \ Release Directory Modules. This will pop-up a dialog that
lets you add your DLL to the list. Now, when you reboot and debug, your DLL
will come from your FRD and not the one in NK.BIN. Combined with Targeted
Builds, this should speed you up a lot.
I use the official PB defined methods to do my building. When you change
something in the registry files the method described below takes less
than 2 minutes.
Here's my when-to-build-what "build shortcut" list:
Change something in Platform Settings: do a makeimg
Change something in a driver in the BSP: Build the driver, do makeimg
Change several things in the BSP: Build the BSP, do makeimg
Change something in the BSP and/or the config files (eg platform.reg):
Build & sysgen the BSP, then Copy Files to RelDir, then Build All
Projects and Makeimg.
Change something in the workspace configuration (add or delete a
component): Sysgen the platform (and sometimes a clean sysgen is needed,
eg when changing from RAM based registry to Hive based Registry).
...and since we can't seem to repeat this enough...
*Never ever* do a build and sysgen on the build menu. Better yet, right
click the menu bar, choose Customize, then click the Build OS menu,
select Build & sysgen and *delete* that option from the build menu.
Hope this helps,
Michel Verhagen, eMVP
EmbeddedFusion
www.EmbeddedFusion.com
mverhagen at embeddedfusion dot com
TiddlyWiki �A�Z支援���� -- 新手请教:如何安装插件
> 看到网络上有很多不同版本的TiddlyWiki
> 还有一些专门的插件,我的问题是如何把这些好的插件安装我所使用的TiddlyWiki中呢,
> 比如这里的一个插件http://www.tiddlytools.com/#SinglePageModePlugin
在�g�[器中�_�⒛愕� TW 文件,
1) TW 2.2.0 建�h�裼么朔绞桨惭b
a.�c�粲疑戏街�「控制台」(backstage)之「��入」(import)
b.「指定伺服器��型」: ���x�� 「file」
c.「����入�W址或路�健�:��入 http://www.tiddlytools.com/, �c�� 「�_��」
d.完成�c伺服器�B��後,再�c�簟搁_��」
e.勾�x列表中的「SinglePageModePlugin」
f.�c�簟���入」、「完成」後,�P�]「控制台」
g.�Υ孀�更後,刷新��面,即完成安�b。
此安�b方式,可利用「控制台」的「同步」功能,��上更新套件,�@是 TW 2.2.0 的��多新功能之一。
2) �鹘y的 TW 套件安�b方式
a.�� http://www.tiddlytools.com/#SinglePageModePlugin 的 �热菁糍N�}�u至新增的文章
(tiddler)中,�⒃�文章的�嘶`�O�� systemConfig ,文章�祟}�t建�h��入��套件名�Q。
b.「完成」����後,「�Υ孀�更」再刷新��面,即完成安�b。
3) �d入外部 js �n形式的套件
a. 在�A�O文章 MarkupPreBody 中��入: <script type="text/javascript"
src="pathto/YourPlugins.js"></script>
(其中,pathto �� YourPlugins.js 套件所在之相�β��矫��Q, YourPlugins.js �樘准��n名)
b.「完成」 MarkupPreBody 的����後,「�Υ孀�更」再刷新��面,即完成安�b。
c.��例���⒖枷铝姓f明中的 MarkupPreBody �热�
我不知道如何加入到我正在使用的版本中ptw-2.2.0-beta4-070319,
查看 MarkupPreBody �e�^即安�b外部套件的方式,
新增一 tiddler ,其�祟}可自��,��入 tiddler �热荩� <<listExtCode>> ,
完成後可看到已安�b之步步�d入之套件。
2) 自 MarkupPreBody �d入的套件,可在欲停用的套件前後加入「<!-- -->」 的HTML�]解�Z法,例如:
<!--
<script ...></script>
<script ...></script>
....
-->
或直接�h除����之 <script ... ></script>
再有;载入外部 js 档形式的套件 ,与内嵌方式;两者有何的优劣如何?
後者相容性高,未�� TW 2.2.0 ��出後,套件更新更��便。
若有多 TW 文件使用�S多同群套件,或 debug 套件�r,可考�]前者。
相�P����可�⒖迹�
http://groups.google.com/group/PrinceTiddlyWiki
(��入搜���l件:「由外部�n案�d入plugins的好��」)
Thursday, March 29, 2007
Monday, March 26, 2007
Sunday, March 25, 2007
Saturday, March 24, 2007
Thursday, March 22, 2007
Tools -- Power Taango 運用特有的系統虛擬與移植技術
軟體版本:Beta 3.0
授權類型:共享軟體
支援語系:多國語言(包含繁體中文)
官方網站:http://www.taango.com/tw/index.htm
檔案下載: 官方網站下載頁面
檔案下載:官方HTTP站下載(6.25MB)
更新日期:2006/7/24
軟體簡介: Power Taango 運用特有的系統虛擬與移植技術,受到國際評審的青睞,榮獲 2006 年美國消費性電子展 CES Show 的創新產品獎,以其強大的移植引擎,可讓您直接將已經安裝在電腦上的軟體, One click 就移植於外接儲存設備中,讓您到任一台電腦上就可直接使用不需重新安裝軟體,離開後資料與軟體就跟著自己離開,就像握在手上的超微小電腦,走到哪我的電腦跟我到哪。
- 軟體移植功能:透過獨一無二的軟體動態移植技術,可以將您電腦上的合法軟體直接移植到外接儲存設備中, 不僅可攜帶軟體本身,還可包含相關的設定及資料,讓您在任一台電腦使用慣用的軟體環境,不會因為設定不同而要費時重新適應,或是陷入沒有軟體可用的窘境 。
- 執行移植軟體:無論走到哪裡 ,您都可以在任何一台 WindowsXP 以上的電腦,直接插上自己的 Power Taango 設備,完全不需安裝即可執行存放的應用程式。
- 安全來去:當您 離開使用的電腦後,應用軟體不會留在該電腦中, Power Taango 會即時移除軟體使用時的相關設定,讓電腦即刻還原,確保電腦的安全性也不會 造成非法散佈軟體的情形。
- 防止非法複製:Power Taango 運用特殊技術將 Power Taango 與移植的軟體加以保護並防止使用者隨意複製到其他非經授權的電腦或其他使用者的設備上,充分在方便性與保護軟體的版權上取得平衡。
- 操作方便, 介面簡易:Power Taango 的介面非常簡易好懂,使用者不需學習就可以上手。
SW -- A source-code analyzer that identifies complex bugs at compile time
CodeSonar
Wednesday, March 21, 2007
Sunday, March 18, 2007
Web2Proxy.net: Free Anonymouse HTTP proxy!
Web2Proxy.net: Free Anonymouse HTTP proxy!
Thursday, March 15, 2007
如何比對兩個excel檔案
http://www.vba.com.tw/plog/
它裡面有寫了一個增益集~是專門比對兩個sheet裡面不同的資料...
...
開兩個檔案然後執行下面的code
MsgBox Workbooks(2).ActiveSheet.Cells(1, 1)
MsgBox Workbooks(1).ActiveSheet.Cells(1, 1)
...
Wednesday, March 14, 2007
ce -- cmd.exe using COM2
I am using Windows CE 5.0 and would like to be able to use the
cmd.exe command processor via COM2.
COM2 is working correctly because a small program which simply echos
characters using ReadFile and WriteFile works fine.
Two methods I have tried were to use
-----------------
Method 1:
A small program which executes the following calls was run.
SetStudioPathW(0, L"COM1:");
SetStudioPathW(1, L"COM1:");
SetStudioPathW(2, L"COM1:");
As was suggested by this post:
http://groups.google.com/group/microsoft.public.windowsce.targeted.de...
However, cmd.exe still seems to be using the keyboard and display for
stdin and stdout after doing this.
--------------------------
Method 2:
http://msdn2.microsoft.com/en-us/library/aa452670.aspx
[HKEY_LOCAL_MACHINE\Drivers\Console]
OutputTo = REG_DWORD:2 // Redirects CMD to COM2
COMSpeed = REG_DWORD:115200 // Speed of serial
connection
I changed the OutputTo value from a '1' into a '2' because my serial
port is COM2
I also changed the example baud rate of 19200 to 115200
up on the display, but also does not seem to send any output to COM2.
The registry settings in "Method 2" is confusing because it uses
decimal values to specify the baud rate. dwords in .reg files are
speced in hex, not decimal so you should add the hex equivalent of the
baudrate into the .reg file.
Henrik Viklund
http://www.addlogic.se