I am compiling webpack and the paths in index.html are as follows
/static/js/main.7c2dc3d5.js
/static/css/main.4a59e0ef.css
My server can't find these files, but when I put a dot in front of /static, everything works fine
./static/js/main.7c2dc3d5.js
./static/css/main.4a59e0ef.css
Same problem with css icons/fonts
by default it puts them as /static/media/
and the icons don't work until I put ../../static/media/
The bottom line is .... where can I edit these paths or who met with the same problem ???
Related
I am trying to create an executable using PackageCompiler.jl. However, whenever I run the command
create_app("src/UnsteadyFlowSolvers.jl","UNSflowCompiled")
I keep getting the error
ERROR: could not find project at "C:\\Users\\Matthew\\OneDrive - Mississippi State University\\Research\\UNSflow\\Ramesh Live\\src\\UnsteadyFlowSolvers.jl"
This is the exact location of the file. For instance:
include("src/UnsteadyFlowSolvers.jl") ; UnsteadyFlowSolvers.julia_main()
works perfectly fine and generates the exact result I would like the executable to return. The Project.toml file is in the current directory if that matters. I have tried an alternate version of the package where the module file is not located in another directory to no avail.
Thanks
create_app(package_dir::String, compiled_app::String; kwargs...)
Compile an app with the source in package_dir to the folder compiled_app.
So the first argument to create_app is the package folder, not the .jl file. I'd suggest a ;cd .. to get outside your project folder, then
create_app("Ramesh Live", "UNSflowCompiled")
I'd like to access the modules directory in /themes/[themename]/modules instead of /sites/default/themes/[themename]/modules/ from [mura]-tag in content
This is Mura Core Version 7.1.438
[mura]dspInclude('themes/[themename]/modules/sprachweiche.cfm')[/mura]
Error 500
Could not find the included template /muraWRM/sites/default/themes/[themename]/modules/sprachweiche.cfm.
To display a registered module, simply use the following syntax, and pass in the directory name of your module.
[m]$.dspObject(object='your-module-directory-name-goes-here')[/m]
That said, in your example though, it doesn't appear to be a valid "module", since you're attempting to include a file called sprachweiche.cfm. So, if you simply want to include a file, I wouldn't put it under the modules directory. So, if you have a directory under your theme called includes, you could use this instead:
[m]$.dspThemeInclude('includes/sprachweiche.cfm')[/m]
This method automatically generates the path to your theme, so you can simply pass in the rest of the path to your desired file.
Cheers!
Thanks Steve
[m]$.dspThemeInclude('includes/sprachweiche.cfm')[/m] caused the error:
Could not find the included template /muraWRM/themes/[themename]/includes/sprachweiche.cfm.
But including the modules directory to the path works:
[m]$.dspThemeInclude('modules/includes/sprachweiche.cfm')[/m]
I am building an ExtJS 4 application backed by SASS/Compass for its theme.
I would like to generate 2 files:
my-ext-theme.css
my-ext-theme.min.css
I currently have a "my-ext-theme.scss" file that I am successfully compiling to "my-ext-theme.css". The issue is that I want 1 scss file to compile to 2+ css files. Additionally, I would like those css files to be in any directory I want.
Note: I do not want to add a config.rb file so that it outputs "only" to different directories (i.e. "css/my-ext-theme.css" and "css2/my-ext-theme.css").
Any suggestions?
Current Solution (little annoying)
my-ext-theme.scss // my sass code here
my-ext-theme.min.scss // #import 'my-ext-theme';
compass compile my-ext-theme.scss // development
compass compile --output-style compressed my-ext-theme.min.scss // production
I have a library and a console application that uses a library. The library has a folder with source and header files.
My project is in a child/inner directory but that library directory that I want to include is in a parent/upper directory.
My project directory:
H:\Gmail_04\gsasl-1.0\lib\libgsaslMain
Includes files are here:
H:\Gmail_04\gsasl-1.0\src
How can I use paths relative to the project directory, to include folders that are in a parent/upper directory?
Instead of using relative paths, you could also use the predefined macros of VS to achieve this.
$(ProjectDir) points to the directory of your .vcproj file, $(SolutionDir) is the directory of the .sln file.
You get a list of available macros when opening a project, go to
Properties → Configuration Properties → C/C++ → General
and hit the three dots:
In the upcoming dialog, hit Macros to see the macros that are predefined by the Studio (consult MSDN for their meaning):
You can use the Macros by typing $(MACRO_NAME) (note the $ and the round brackets).
If I get you right, you need ..\..\src
I have used a syntax like this before:
$(ProjectDir)..\headers
or
..\headers
As other have pointed out, the starting directory is the one your project file is in(vcproj or vcxproj), not where your main code is located.
By default, all paths you define will be relative. The question is: relative to what? There are several options:
Specifying a file or a path with nothing before it. For example: "mylib.lib". In that case, the file will be searched at the Output Directory.
If you add "..\", the path will be calculated from the actual path where the .sln file resides.
Please note that following a macro such as $(SolutionDir) there is no need to add a backward slash "\". Just use $(SolutionDir)mylibdir\mylib.lib.
In case you just can't get it to work, open the project file externally from Notepad and check it.
There are a couple of hints you need to know.
consider your app is running under c:\MyRepository\MyApp
a single dot on your path means the folder where your app runs. So if you like to reach some folder or file under MyApp folder (imagine c:\MyRepository\MyApp\Resources\someText.txt) you can do it like var bla = File.Exists(./Resources/someText.txt)
and you can go one level up with double dots (..) think about a folder under c:\MyRepository\SomeFolder\sometext.txt
for MyApp, it will be like
var bla = File.Exists(../SomeFolder/someText.txt)
and it is possible to go 2,3,4.. levels up like
../../SomeFolder (2 levels up)
../../../SomeFolder (3 levels up)
and path starting with no dots means the drive root. var bla = File.Exists(/SomeFolder/someText.txt) will look for the c:\SomeFolder\someText.txt in our scenario.
I need to use a file for one of my tests written using Check. I initially hardcoded the path, which worked fine. However, this didn't work when the code is built outside of the source directory. I came up with the following solution which somewhat works. (I then prefix pathnames with TESTS_DIR)
# Set correct directory for test files
AS_IF([test "x$srcdir" = x.],
[TESTS_DIR=""],
[TESTS_DIR="$srcdir/tests/"])
AC_DEFINE_UNQUOTED([TESTS_DIR], ["$TESTS_DIR"], [directory for test files])
Unfortunately, this fails again for make distcheck. I could post specific path layouts and structures, but I'm wondering if there's an "easy" way to refer to files in the source directory in all these cases. Thanks!
UPDATE: I've tried to use absolute paths, but it seems $abs_top_srcdir isn't set when I tried to update the define in configure.ac. Any thoughts as to why that is would be appreciated.
I discovered that the problem was that $top_srcdir is not set at configure time. Instead, I added -DTESTS_DIR="\"$(top_srcdir)/tests/\"" to AM_CFLAGS in my tests Makefile.am and also added all directories containing test files to EXTRA_DIST.