Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 472
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3368: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:472)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3370: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:472)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3371: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:472)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3372: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:472)
OrbWorks Community Forum • View topic - Distribution Anyone?
Page 1 of 1

PostPosted: Wed Oct 02, 2002 10:11 am
by chrisleeuk
On the way home on the train I was thinking over the issues involved in getting Pocket C applications onto other machines. (I am still trying to decide if Pocket C will be powerful enough to allow be me to develop full applications)

I am aware of the use of CAB files and have some idea how they are created using CABWIZ. I know about different processor issues.

Does anyone have any answers to the following questions?

(1) Detect if Pocket C runtime is installed and if not install it (using the CAB files possibly?)

(2) If I want to distribute the CEAPI DLL can I just add it to the CAB file (sending it to the windows folder) and that will be enough
or I need to register the DLL as in PC Windows?

(4) I also have a PC Visual Basic based RAPI routine from Microsoft which can copy files directly to the Pocket PC via ActiveSync and (RAPI.DLL)

If automatically installing the Pocket C runtime cannot be done in the CAB file might RAPI offer a solution to installing Pocket C automatically?

(5) What methods are people using to get Pocket C programs onto other possibly Pocket C free Pocket PC's? (Try saying that last bit fast :D)

Phew! I think I will go for a rest now.

PostPosted: Wed Oct 02, 2002 1:19 pm
by guy
There is a CEAPI distributors kit that includes the file for creating CAB files for applications that use CEAPI, just plug in your own application name. You can download this from the CEAPI download page.

This could easily be updated to also install the PocketC runtime as well. Kevin has distributed the INF file for the PocketC modules. The only problem is that he hasn't distributed a convenient package of the varius runtimes. What you have to do is download every PocketC runtime CAB file and extract each of the files into an appropriate directory and set their names.

I've been meaning to do this for a while, but it's a bit tedious and I'd have to do it again every time there was a runtime update (so once every five years then...).

1. You don't need to detect whether the runtime is installed. If you include a line for it in the INF file for the CAB, and it's already installed then it won't be installed again (although as shared files their reference counts will be updates).

2. Look at the CEAPI distribution kit zip file contents.

4. You can use RAPI, but it's easiest to just let CEAppMgr do it in combination with EZSetup (see the CEAPI distribution kit builder readme).

5.1. You can include the runtime CAB files or all-in-one kit as well as your own and get the user to install both.
5.2. You can tell the user where to find the runtime
5.3. You can build the runtime into your installation
5.4. You can offer the user a choice on download so that they only need to download the bits that they need.

I'll go and see whether I can find that INF file of Kevin's.


Guy
[url]mailto:pcform@pcform.net[/url]
http://www.pcform.net
PocketC CE API interface: http://www.networkdynamics.net/PCForm.html#library
PCForm and CE API forum: http://www.networkdynamics.net/forum

PostPosted: Wed Oct 02, 2002 1:26 pm
by guy
Found the INF file(s). Actually put them where I thought I had. This is a level of organisation unexpected for me.

Kevin has written one INF file for each platform. I'll see whether I can merge them into the CEAPI distribution INF file and comment them out.


Guy
[url]mailto:pcform@pcform.net[/url]
http://www.pcform.net
PocketC CE API interface: http://www.networkdynamics.net/PCForm.html#library
PCForm and CE API forum: http://www.networkdynamics.net/forum

PostPosted: Wed Oct 02, 2002 1:28 pm
by guy
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">

(I am still trying to decide if Pocket C will be powerful enough to allow be me to develop full applications)

<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

What do you need it to do?


Guy
[url]mailto:pcform@pcform.net[/url]
http://www.pcform.net
PocketC CE API interface: http://www.networkdynamics.net/PCForm.html#library
PCForm and CE API forum: http://www.networkdynamics.net/forum

PostPosted: Wed Oct 02, 2002 1:49 pm
by chrisleeuk
With regard to the 'What do you want it to do?'
I have been looking at different development tools for use on the Pocket PC with the view to the development of a shareware application.

I like the idea of coding on the device as I spend a fair amount of time waiting around waiting for transport on the way to my real job as an internet application developer.

At this stage I am simply giving the language a try to get some feel of its abilities. I can tell you now that it is a lot better in terms of memory that such as EVB.

Since you don't end up with an .EXE file with Pocket C I am now looking at the distribution issues because I want to be confident this will not be a problem.

Thankyou for the tips!
I will be taking a look at your answers when I have the chance.

PostPosted: Wed Oct 02, 2002 4:00 pm
by guy
I've extracted all of the PocketC runtime variants and arranged that they will be included in the next CEAPI kit builder distribution.

This will let you build a single kit that will install a PocketC application without the end user needing to install the CEAPI runtime or the PocketC runtime. Clean and simple.

Just uncomment the appropriate lines in the INF file, add the names of your app files and that's it. Contains sections for start menu items, help menu items and all the other usual stuff.

You can use this even if your app doesn't need CEAPI.


Guy
[url]mailto:pcform@pcform.net[/url]
http://www.pcform.net
PocketC CE API interface: http://www.networkdynamics.net/PCForm.html#library
PCForm and CE API forum: http://www.networkdynamics.net/forum

PostPosted: Thu Oct 03, 2002 7:43 am
by chrisleeuk
When you mention 'the next API distribution' do you mean this is available now or will be soon. If so when?

Thanks Again
Chris

PostPosted: Thu Oct 03, 2002 11:14 am
by guy
Depending on the speed of the compiler on my ageing 450mhz machine, it may be today or tomorrow. I have to compile 16 combinations of CPU/Device type/CE version for the library.


Guy
[url]mailto:pcform@pcform.net[/url]
http://www.pcform.net
PocketC CE API interface: http://www.networkdynamics.net/PCForm.html#library
PCForm and CE API forum: http://www.networkdynamics.net/forum