Awesome! I should asked about that long time ago.
Thanks for letting me know.
-Kun
--- On Tue, 6/9/09, Nicolás Alvarez wrote:
> From: Nicolás Alvarez
> Subject: Re: [boinc_dev] Any idea about Compile BOINC Application in Windows
> with Visual C++ 6.0
> To: "Kunsheng Chen"
> Cc: boinc_d
El Lunes 08 Jun 2009 21:50:19 Kunsheng Chen escribió:
> The thing is that it require Cygin1.dll to be under folder Windows/System32
> in client side. I think I could have a multiple bionc app (includes this
> cygwin1.dll). And in my app, just copy Cygwin1.dll to Windows/System32, but
> this seems w
> What I am trying to do is a stand-alone app in Windows , so cygwin is not
> working (require cygwin.dll), For MinGW, I have PCRE and libcurl in my app,
> which is hard to compile there. Visual C++ is what looks best to me
> currently. So I am really confused what I should do next.
---
2009/6/8 Nicolás Alvarez
> El Lunes 08 Jun 2009 21:30:01 Jeremy Cowles escribió:
> > Maybe I'm not understanding something, but under windows files must end
> in
> > .bat to be executed as a batch file, correct?
> > If this is the case, are batch files are not supported by
> update_versions?
> >
El Lunes 08 Jun 2009 21:30:01 Jeremy Cowles escribió:
> Maybe I'm not understanding something, but under windows files must end in
> .bat to be executed as a batch file, correct?
> If this is the case, are batch files are not supported by update_versions?
> I ask because the reg-ex that parses exec
El Lunes 08 Jun 2009 21:27:53 Kunsheng Chen escribió:
> Thanks, Nicolas.
>
> I am still confused about the following things:
>
> 1. Does client have to install .NET if I compiled my BOINC app through
> Visual Studio 2005 / 2008 ?
No, they don't need .NET, unless your app is actually written with t
Maybe I'm not understanding something, but under windows files must end in
.bat to be executed as a batch file, correct?
If this is the case, are batch files are not supported by update_versions? I
ask because the reg-ex that parses executable names does not include .bat as
an option. See: re_match
Thanks, Nicolas.
I am still confused about the following things:
1. Does client have to install .NET if I compiled my BOINC app through Visual
Studio 2005 / 2008 ?
2. I am not sure how other Windows-compatible BOINC App works. Do they
actually require .NET ?
What I am trying to do is a st
El Lunes 08 Jun 2009 21:03:08 Kunsheng Chen escribió:
> I just checked some guidance online, seems they require Visual Studio 2008/
> 2005 or 2003. What I am concerned about is the compiled application with
> Visual Studio, does it require .NET Framework installed in client side ?
No. In fact, you
Hello everyone,
I am going to port my current Linux-compatible BOINC Client Application into
Windows.
I just checked some guidance online, seems they require Visual Studio 2008/
2005 or 2003. What I am concerned about is the compiled application with Visual
Studio, does it require .NET Framew
Hi,
I've been thinking for a while about the possibility of having
recurring payments implemented in BOINC, pretty much the same way
single donations are implemented right now, via paypal. The idea is to
have donors setup something like a monthly donation that takes place
automatically. Each user
Tools that should run by hand are installed under $(bindir). Daemons
that are managed by 'start' go to $(libexecdir)/sched. The (F)CGI stuff
goes to $(libexecdir)/cgi-bin. Finally, example applications go under
$(libexecdir)/examples.
---
apps/Makefile.am |3 ++-
sched/Makefile.am | 41
Let them live in /py/Boinc. make_project now generates
/bin/boinc_path_config.py that makes sure the pyhton
interpreter will find the modules.
---
py/Boinc/setup_project.py |9 -
sched/assimilator.py |3 ++-
sched/start |3 ++-
sched/testasm.py |
It is now possible to use the same set of tools for multiple projects by
setting BOINC_PROJECT_PATH.
---
py/Boinc/boinc_project_path.py | 37 +
sched/assimilator.py |4 ++--
sched/start| 19 ---
tools/parse_c
'start' now looks for programs to execute in $PATH, so the same set of
binaries can be used to handle multiple projects. /bin is
always prepended to $PATH to ensure that project-specific binaries
always take precedence.
---
sched/start |9 ++---
1 files changed, 6 insertions(+), 3 deletion
> That's right - it's needed for make_project and upgrade,
> which means you need to run configure first.
> It would be nice to get rid of this requirement.
Ok, here is a set of patches that begins to convert the BOINC server
from the current "run 'make' & copy from the source/build directory" to
Add an '--srcdir' option to make_project and upgrade that allows
specifying the source directory if the commands are being run from some
other location. Exit with an error if --srcdir is not given and the
current directory does not look like a BOINC source directory.
---
configure.ac
Also clean up the py/Boinc directory by moving the files that are not
part of the Boinc package one level up.
---
configure.ac | 13 ++---
py/Boinc/Makefile.am | 25 -
py/Boinc/boinc_path_config.py.in | 12
py/Boinc
18 matches
Mail list logo
