Bug #2602
closedWrong wthttpd Config File Location (win32 precompiled installer)
0%
Description
(Followup to #2593)
I am on Win7, used the installer
Wt-3.3.1-msvc2010-Windows-x86-SDK-build-1
Compiled a simple test app.
Problem:
The config-file-location (retrieved via: mywttest.exe ---help) is set to :
c:/pau/winstng/build2010-x86/prefix/etc/wt/wthttpd
Should be:
c:/witty/wthttpd
(I can workaround by simply creating this directory-tree and placing the file there)
Updated by Wim Dumon over 11 years ago
- Status changed from New to Resolved
you can set it yourself, by not using WRun, but instantiating the server yourself. How your own MyWRun should look like is documented here:
http://www.webtoolkit.eu/wt/doc/reference/html/classWt_1_1WServer.html
The third parameter of setServerConfiguration is the path to the filename.
Precompiled Wt needs indeed a fix for this.
Updated by I. Lazaridis over 11 years ago
Wim Dumon wrote:
Precompiled Wt needs indeed a fix for this.
ok.
I am wondering about your workflow here (Status changed from New to Resolved). Usually, "resolved" is set when the bug is fixed in the repo (pointing to the changeset).
Updated by Wim Dumon over 11 years ago
I fixed this indeed in the winstng git.
Resolved = fixed in git
Closed = fixed and released in an official version
Best regards,
Wim.
Updated by I. Lazaridis over 11 years ago
You don't point to the commit here?
Additionally, I noticed that wt is on github:
https://github.com/kdeforche/wt
I'm a bit confused about the repo's, is this one the main winstng repo?
Updated by Wim Dumon over 11 years ago
winstng is a tool that builds wt and all of its dependencies. It's a combination of shell scripts and cmake files.
The github repository that you refer to is the wt git repository.
BR,
Wim.
Updated by I. Lazaridis over 11 years ago
I try to locate the commit of your fix for this issue.
Can you please provide a link?
Updated by I. Lazaridis over 11 years ago
ok.
btw: I noticed that the blog main code contains a relevant line, which can be set to:
server.setServerConfiguration(argc, argv, "c:/witty/wthttpd");
So, working around is trivial.
Updated by Wim Dumon over 11 years ago
Like I wrote in my first response? ;-)
Wim.
Updated by I. Lazaridis over 11 years ago
No exactly.
You pointed to the doc.
I gave the relevant code example (after grasping it), making this way the workaround simpler for newcomers.
Updated by Koen Deforche about 11 years ago
- Status changed from Resolved to Closed