To add to the above info:
I am using Visual Studio 2008 Team Suite Trial version (90 days I
suppose)...
- A quick look at the wiki link provided states that wt can be run without
any problems on Visual Studio 2005/2008 professional and express editions. I
presume that team system would not have any issues as such...
- The command arguments...
--http-address=0.0.0.0 --http-port=8080 --deploy-path=/hello --docroot=.
what is the meaning of each of them?
-http-address=0.0.0.0 is pretty straight forward which gets a default ip
address
-http-port=8080 tells the internet port number
-deploy-path=/hello -docroot=. is a bit confusing and there might be an
error here...But I suppose these are standard VS command prompt necessities
for running a debug exe?
Thanks and Regards,
Bhushan
On Mon, Oct 12, 2009 at 5:02 PM, Bhushan Inamdar <[email protected]>wrote:
> Hey all, I finally tried to build Hello.wt after going through the steps
> exactly mentioned on the wiki link given below. Since I had already got the
> Visual Studio build and source files from CMake, all I had to do was to
> follow the remaining steps. Thus I started by selecting *Project |
> Properties | Debugging* entering:
> --http-address=0.0.0.0 --http-port=8080 --deploy-path=/hello --docroot=.
> in the '*command arguments' *text box. I then set up HelloWt as my start
> up project and then I put a break point on the line...
> return WRun(argc, argv, &createApplication);
> I get a pop up console window in which I get the following message:
> Error: Adjacent parameter is empty in 'http-port'
> On debugging further it goes into crtexe.c at the line...
> mainret = main(argc, argv, envp);
> Stepping further mainret gets a value of "1" and moves on to :
> if (!managedapp) exit (mainret);
> where since this is not a managed app, it enters the loop and value of
> mainret i.e., 1 is passed on to exit...which is why it exits...I even tried
> to step into further depth to find out the function call where the exception
> occurs, but it simple exits...
> The output window shows the following C++ exceptions:
>
>> -First Chance Exception at 0x7c812aeb in hello.wt.exe: Microsoft C++
>> exception: boost::program_options::invalid_command_line_syntax at memory
>> location 0x011ff10c
>>
> -First Chance Exception at 0x7c812aeb in hello.wt.exe: Microsoft C++
>> exception: Wt::WServer::Exception at memory location 0x011ff888
>
> I have absolutely no clue of what that means...
> In the meantime it does not pop up the browser and show the Hello
> page...and even when I put a break point and start a browser and type in
> http://127.0.0.1:8080/hello, the page is not displayed. That said, I
> think, I have been little optimistic trying to run the application without
> getting rid of debug errors.
> I think I am missing the trick and the key lies in the console that pops up
> while debugging saying that "Error:Adjacent parameter is empty in
> 'http-port'...must be refering to 8080...So I asked before, if I have any
> issues with my Xp Home Edition...
> However, I am not sure what is really happening and I still feel that I am
> very close to running the application. So please let me know what is it that
> I am supposedly missing here. One thing I noticed, that may be useful in
> trouble shooting is, I have Apache hosting server installed on my computer.
> Is there any setting that prevents me to use port 8080 outside or besides
> Apache? Is port sharing allowed in Apache? Please let me know the correct
> way to go about this and put a smile on me...
> Thanks and Regards,
> Bhushan
>
>
>
>
> On Sat, Oct 10, 2009 at 3:32 PM, OvermindDL1 <[email protected]>wrote:
>
>> On Sat, Oct 10, 2009 at 4:00 AM, OvermindDL1 <[email protected]>
>> wrote:
>> > On Sat, Oct 10, 2009 at 3:14 AM, Wim Dumon <[email protected]> wrote:
>> >> In addition to Overmind's reply: There is a wiki page that describes
>> >> the installation process on a clean windows PC in detail:
>> >>
>> http://www.webtoolkit.eu/wt/wiki/index.php/Installing_Wt_2.1_on_MS_Windows
>> >>
>> >> It even covers the installation of the compilers and all required
>> >> dependencies. Always interested to hear if these don't work for you...
>> >
>> > Ah, I did not see that page, it seemed quite painless to me though,
>> > seems like a well designed library.
>> >
>> > The Wt crash when missing the config file happened just after the stat
>> > call, it started to create the parser for the file, but never
>> > initialized the memory for it, and ended up crashing when it tried to
>> > read an std::string. I fixed that rather quickly (and recompiled Wt
>> > to point to some place other then a C: drive as a default location, I
>> > do not have a C: drive, my boot drive is G: and my windows install is
>> > on F:, don't ask, this computer is an evolution of 15 years of
>> > upgrades...). It might have been due to more of the drive missing
>> > rather then the file, I am not sure how stat handles that (I am not
>> > sure why stat is being used, why not just open the file without
>> > creation and see if you get a valid handle back, it is supposed to be
>> > more optimized to do it that way as well).
>> >
>> > I did notice some places where Spirit.Classic is used. If you
>> > upgraded it to Spirit2.1 (or 2.2 in trunk) you would be a rather
>> > significant speed boost in execution speed for that code (Spirit2.x
>> > outperform Spirit.Classic by *far*, and it is a lot easier to use as
>> > well). If you wish I could bcp out the Spirit2 code so it is
>> > self-contained (I could actually do that to all the used boost
>> > libraries if you wish, then you would not need boost as a requirement,
>> > although everyone should have it anyway in my opinion) in case they do
>> > not have 1.41. I could easily make the conversion if you are curious,
>> > I know Spirit *very* well.
>>
>> Also if you upgraded Boost.Signal to Boost.Signal2 you would also get
>> a healthy speed-boost as well (requires some code changes). Signals1
>> has a lot of inefficiencies that hobble it down, hence the redesigned
>> Signals2 being vastly more efficient (and can be properly thread-safe
>> too if you so wish, unlike Signals1).
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> witty-interest mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/witty-interest
>>
>
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
